> For the complete documentation index, see [llms.txt](https://docs.getkita.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getkita.org/getting-started/what-is-kita.md).

# What is Kita?

Kita is a platform for teaching Computing that lets teachers set programming work, assess it, and return feedback without moving between systems.

It starts by keeping all the materials in one place.&#x20;

A lesson in Kita holds the instructions students read, the workspace where they write Python, the tests their programs must pass, the activity they submit to, the rubric it is marked against, and the feedback that comes back.&#x20;

Because all of that is attached to one lesson, the assessment cycle never leaves the platform — which is what makes fast, specific feedback practical for a full class.

### Why this matters

Code editors work well because code is self-contained. Teaching is not.

Teaching is fragmented across systems. The editor holds the code, the VLE holds the task, a shared drive or inbox holds the submissions, and a spreadsheet holds the marks. Each system operates independently, with no shared understanding of how they connect.

Without that connection:

* A tool that only sees the code cannot tell whether the work was submitted, or submitted on time
* A tool that only holds the assignment cannot tell whether the program actually runs
* Feedback ends up separated from the code it refers to, so students read it without the work in front of them
* Every handoff between systems is manual, and the cost is paid per student, per lesson

Giving students a code editor is not enough. Assessment needs the task, the code, the tests and the mark scheme in the same place, tied to the same piece of work. That is what a Kita lesson is.

### The lesson as the unit

When you build a lesson in Kita, everything the assessment cycle needs is attached to it:

* **Instructions** students read as they work, written and edited in the lesson editor
* **A Python and JavaScript workspace** in the browser, with no installation on school machines. More languages to come, and [check out our list of libraries](https://docs.getkita.org/guides/supported-languages-and-libraries.md).&#x20;
* **I/O tests** — inputs and their expected outputs, which run when a student triggers a test run
* **A code submission**, if the lesson is setup for submissions students can submit: .py, .js, .txt, .csv, rtf, and a kita-specific format: worksheet&#x20;
* **A rubric as part of code submissions**, with criteria, levels and points&#x20;
* **Quizzes**, allowing students to take both short and longer quizzes. This can be both self-contained or used alongside a coding activity.&#x20;
* **AI Help settings** that apply to this lesson and no other
* **Every submission**, whether it be a code submission or a quiz and the feedback returned against it.&#x20;

Because the lesson holds all of this, the work never has to be exported, renamed or re-uploaded.&#x20;

A student's code submission arrives already attached to the task where it was set.&#x20;

When a student's program produces an error, Kita shows the standard Python error output rather than a simplified substitute, so students practise reading the errors they will meet outside the classroom.&#x20;

#### What the teacher sees...&#x20;

This is the left files pane where you manage files in Kita.&#x20;

<figure><img src="https://1176288822-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjzm9nyD2lhxeWS1B64j9%2Fuploads%2FZ1cRqAVKdZf0KLyvEoWh%2Fimage.png?alt=media&amp;token=13f70ea7-e833-4ff8-b035-1abb26ebeb3e" alt="Shows the left-hand file area in a lesson. A main.py file is shared with students as a template, solution.py is hidden from students, glossary and instructions are only editable by a teacher." width="375"><figcaption></figcaption></figure>

#### What the student sees in the same lesson...&#x20;

Students have a simplified view, so they only see and edit what you want them to see and edit.&#x20;

<figure><img src="https://1176288822-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjzm9nyD2lhxeWS1B64j9%2Fuploads%2FanVQ2E6qr4yP56u8GuMN%2Fimage.png?alt=media&amp;token=4f548d84-90e2-49cc-b376-03a7a79818ba" alt="Student view of the left sidebar in the lesson IDE. The top file main.py has been submitted by the student. There is a Supporting files folder including &#x27;example.py&#x27; which is read-only. " width="375"><figcaption></figcaption></figure>

### How AI supports students safely

Kita's AI support is called **AI Help**. It is off until a teacher turns it on, and it is configured for each lesson rather than for the platform.

This is the design decision that separates Kita from a general-purpose assistant. The teacher decides, lesson by lesson, how much help is available:

* **Off by default.** AI Help does nothing until a teacher enables it on a specific lesson.
* **Each mode is independent.** Explain, Debug, Tutor and Hints can be switched on or off separately, so a lesson can offer error explanations without offering hints.
* **Hints escalate through capped levels.** Support starts at the gentlest nudge and only increases if the student is still stuck. The teacher sets the maximum level the AI may reach.&#x20;
* **Tutor mode asks rather than answers.** When a student expresses confusion, the Tutor agent responds with structured questions that prompt independent reasoning instead of supplying the solution.
* **Feedback generation is teacher-triggered.** The teacher chooses the style, length and format, and starts the generation. Students do not generate their own feedback.&#x20;
* **Setting the 'year' (educational level) on your course customises the feedback.** This helps the AI to have a reading age appropriate to the level you select, you can then customise this further using per group and/or per student AI settings in your courses.&#x20;

The four hint levels are what make the cap meaningful:

**Level 1 — Gentle Nudge.** A broad reminder of relevant programming ideas, with no reference to the student's own code.&#x20;

**Level 2 — Conceptual Hint.** A pointer toward a specific concept, or a possible problem in their approach.&#x20;

**Level 3 — Contextual Hint.** A response that refers directly to the student's code and the logic they are implementing.&#x20;

**Level 4 — Guided Next Step.** An explicit instruction about the next change to make.

A lesson capped at L1 or L2 keeps the reasoning with the student. A lesson capped at L4 is closer to guided practice. The choice belongs to the teacher who knows the class.

This is not a chatbot with a content filter attached. The lesson settings and the AI's behaviour are the same system, so the limits are structural rather than advisory.

For the settings themselves, see [Update the AI settings for a lesson](https://docs.getkita.org/set-up-your-lesson/update-the-ai-settings.md).

### Teaching and assessment

Alongside the workspace, Kita provides the structure teachers need to run a class and mark its work. Three concepts carry most of it: **courses define what you teach, classes and subgroups define who you teach it to, and code submissions define what gets marked.**

#### Courses and lessons

A course is a container for related lessons. A lesson is a single unit of teaching — instructions, a workspace, and optionally a code submission where students hand-in.&#x20;

**Guides coming soon:**&#x20;

* Creating a course&#x20;
* Customising your lessons

#### Classes

A class is how students get into Kita. You create the class, enrol it onto the courses the class should see, and share a join link or add students. Students use the invite link to join Kita and the courses you enrolled the group onto appear for them.&#x20;

For more on this, [Add your students to Kita](https://docs.getkita.org/set-up-your-class/add-your-students-to-kita.md).

#### Code submissions

A code submission is what makes work submittable and markable.&#x20;

Creating a code submission lets you set a due date shown to students, the filenames you expect, how many I/O tests must be run or passed before submission, and the rubric the work is scored against. You can save it as a draft or publish it to students.

Expected filenames are a guide rather than a restriction: work submitted under a different name is still accepted, and a student who submits the wrong file can submit a replacement without waiting for the teacher.

**Guide coming soon:**&#x20;

* Create an assessed activity&#x20;
* Create a quiz, test, or exam

### Student work and feedback

Submitted work arrives in **Student work >** **Marking** where you find an area for each course. Code submissions and Quiz submissions are in the same area so that you can look at work side-by-side.&#x20;

**For code submissions:** you open a student's submission, score it against your rubric, and return feedback.&#x20;

**For quiz submissions:** these are typically auto-marked and either auto-released or reviewed by you as the teacher first. Where long-form text questions are included these are currently marked manually.&#x20;

There are three routes into a student's work, and which one you use depends on what you are doing:

* **People** — live teaching, watching the class code during the lesson
* **Student progress** — asynchronous checks between lessons
* **Student work > Marking** — working through submissions for an assessed activity

When AI generates feedback, three settings shape it, chosen independently of one another. **Style** is Concise, Supportive or Structured. **Length** is Shorter, Medium or Longer. **Format** is Standard prose or 2 Stars and a Wish. The defaults are Supportive, Medium and Standard.

If a student submits the wrong file, **Unsubmit** returns the work to them. Kita also accepts multiple submissions, so in most cases a student can correct the mistake without teacher intervention.&#x20;

<figure><img src="https://1176288822-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjzm9nyD2lhxeWS1B64j9%2Fuploads%2FKhZ2YzRxziqMXu21OHHh%2Fimage.png?alt=media&amp;token=8e3ff66c-a2d2-4ec7-8c92-161ef3f8bf08" alt="Two students have been selected in the submission list for their work to be unsubmitted by the teacher."><figcaption><p>In this example, two students have submitted work and the teacher wants to unsubmit so that students make revisions and the resubmit.</p></figcaption></figure>

**Guides coming soon:**&#x20;

* Marking code submissions
* Marking quizzes

### Kita for Schools and Open Kita

**Kita for Schools** is the licensed edition. Your school gets its own instance, with class groups, assessed activities, marking and administrative controls, governed by the Kita for Schools terms and privacy policy.

**Open Kita** is a free version for basic coding and is available at: <https://getkita.io/try>

### What Kita is not

* **Not a general-purpose AI chatbot.** AI Help is scoped to a lesson, and the teacher decides which modes are available and how far hints may go.
* **Not a plagiarism detector yet, although we are working on tools to help.** Kita does not judge whether submitted work is a student's own.
* **Not a virtual learning environment.** Kita covers Computing lessons, assessment and feedback. It does not replace your school's VLE or MIS.
* **Not an installation.** There is nothing for students to install. Kita runs in a browser.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.getkita.org/getting-started/what-is-kita.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
