Skip to main content
Kai Code is built to work from the inbox. Every bug report, feature request and inquiry carries a Kai Code card in its sidebar: “Kai picks up this ticket, fixes it, and reports back.”

​
Fix with Kai Code

Choose Fix with Kai Code on the card. The Kai Code composer opens over the ticket with the headline “Let Kai Code handle #1234!” and the ticket already attached — its description, conversation, reporter details, screenshots, replay and console logs are Kai’s context. The repository chip starts as Repos: Auto: Kai picks the right repositories from the ticket when you send; add one to choose yourself. Add any instructions and send. The session runs like any other: Kai plans, asks when it needs a decision, changes code and opens a pull request. Sessions started from a ticket are visible to the whole team. Only one session can run per ticket at a time. While one is active the card shows Open running session instead.

​
Following along

Below the composer the card lists every session linked to the ticket with its state, when it last changed, a Preview link when a preview is running, and the Kai Verify verdict. Open a session to read the transcript or steer it. Inside a session, Ticket (T) jumps back to the ticket.

​
Hand over to your coding app

The chevron next to Fix with Kai Code offers the same task in your own tool: Open in Claude Code, Open in Codex or Open in Cursor. Gleap opens the app with the ticket context; status and pull requests sync back to the ticket through the Gleap MCP server. Your last choice becomes the button’s default.

​
From Kai Resolve

When Kai Resolve investigates a ticket and concludes that code needs to change, its card carries the same Fix with Kai Code button. It opens a new session with the investigation as the prompt and the suggested repositories attached. Kai Resolve steps back once the coding session starts.

​
After the pull request

You review and merge in GitHub, Azure DevOps, GitLab or Bitbucket as usual. On merge, Gleap follows your Customer replies setting: a teammate verifies the fix is live and Kai drafts the reply, Kai replies automatically after the deployment delay, or nothing is sent. If the customer later reports that the fix needs more work, the Kai Code card shows their feedback with Continue coding session — one click reopens the session with the feedback inserted.

​
Requirements

  • The Kai Code plan feature; without it the card offers Start Kai Code with an upgrade.
  • The Kai Code cloud permission for cloud sessions, granted through roles.
  • At least one connected repository in the project.