> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gleap.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Kai Code

> The coding agent inside Gleap — it investigates tickets in your codebase, ships fixes as pull requests and reports back to the customer.

Kai Code is Gleap's coding agent. It reads your repositories, investigates a bug report or feature request, makes the change, verifies it in a running preview and opens a pull request — right from the ticket in your inbox. Once the pull request is merged, Kai can tell the customer their issue is fixed.

```
Ticket  →  Kai Code session  →  Pull request  →  Merge  →  Customer reply
```

## What it does

<CardGroup cols={2}>
  <Card title="Fix tickets" icon="wrench" href="/documentation/kai-code/tickets-and-pull-requests">
    Start Kai Code on any bug, feature request or inquiry. It picks up the ticket with its context, finds the right repository, fixes the issue and reports back.
  </Card>

  <Card title="Plan, then build" icon="list-check" href="/documentation/kai-code/sessions#plan-and-build">
    New sessions start in **Plan** mode: Kai drafts a plan you review before it touches code. Switch to **Build** for direct edits and pull requests.
  </Card>

  <Card title="Verify visually" icon="video" href="/documentation/kai-code/sessions#kai-verify">
    Kai Verify runs your app, clicks through the change and records video and screenshots as evidence. Results can be posted to the pull request.
  </Card>

  <Card title="Close the loop" icon="reply" href="/documentation/kai-code/customer-replies">
    After the merge, a teammate verifies or Kai replies automatically after your deployment delay — using your reply instructions.
  </Card>
</CardGroup>

## Where it runs

Kai Code sessions can run in two places, and every teammate chooses for themselves:

* **Kai Code Cloud** — Gleap's sandbox. Nothing to install, always available, billed in your project's **AI credits**.
* **Kai Code Bridge** — your own computer or server, with your own **Claude Code, Codex or Cursor** subscription and your local checkouts. Not billed by Gleap. See [Kai Code Bridge](/documentation/guides/kai-code-bridge).

You can also drive tickets from your own coding app: the ticket's Kai Code button offers **Open in Claude Code**, **Open in Codex** and **Open in Cursor**. Status and pull requests sync back to the ticket.

## Install the Gleap SDK with Kai Code

Kai Code can also install Gleap itself. On the widget installation page choose **Install with Kai Code**, connect the GitHub repository of your app, and Kai opens a ready-to-merge pull request that adds the SDK — for web apps, websites and mobile apps.

## Start here

1. [Getting started](/documentation/kai-code/getting-started) — the setup wizard: repository, tools, customer replies.
2. [Sessions](/documentation/kai-code/sessions) — the composer, plan review, verification and pull requests.
3. [Tickets and pull requests](/documentation/kai-code/tickets-and-pull-requests) — Kai Code inside the inbox.

## Plan and permissions

Kai Code is part of the **Kai Code** plan feature. Without it the Kai Code page shows an upgrade card, and a 14-day trial can be started once per workspace. Access is controlled by the **Kai Code** permission group in roles: seeing the Kai Code page, running cloud sessions, using local models and changing settings are separate permissions.