Login
Start free trial
Kai Code Software engineer

The AI coding agent for customer feedback.

Ticket in. Pull request out. Turn confirmed bugs and approved requests into code changes and pull requests, with the customer context attached. Your engineers review, merge and ship.

4.6/5 on G2
Trusted by 4,500+ teams worldwide
Start free trial
See it work

7 days free. Cancel anytime.

Connect a repository and start the first session from a ticket.
Start free trial
Trusted by 4,500+ teams
From ticket to pull request. Kai Code plans the change, writes the code and opens the pull request inside the ticket. Your engineers review and merge.
Customer issue
Answer & route
Investigate
Build & test
Gleap team memberGleap team memberGleap team memberReview & ship
Customer follow-up
Read the evidencePlan and codeOpen the pull request
Kai Code · Context

Starts with the evidence.

The ticket, the conversation, device details, attachments and your repository. A coding task from Kai Resolve adds what its investigation found in the logs and the code.

13:24:30 Feedback received
13:24:03 cart.items undefined
13:24:02 500 POST /api/orders
13:23:54 pageView
13:23:50 Retrying (2/3)
13:23:43 sessionStarted
13:23:39 User logged in.
Kai Code · Changes

Plans, then writes the code.

Kai Code works out the change, edits the code and shows the changed files in the ticket. Some models also offer a plan step before building.

Kai Code · Pull request

Opens the pull request in the ticket.

The pull request lands next to the customer conversation with a summary and the diff. Your engineers review and merge.

Three ways to run it.

Hosted by Gleap, on your machine, or in your coding tool.
Hosted by Gleap. Start a session from the dashboard or the mobile app and get a push when the pull request is ready.
Your computer or server and your Claude Code, Codex or Cursor login. Pair it once with a device code.
A deep link opens the ticket in Claude Code, Codex or Cursor. Progress reports back through the Gleap MCP server.

Try the fix before you merge.

Branch previews on Kai Code Bridge.
On a Kai Code Bridge session, Start preview runs the branch on your paired machine. Kai Code can check its own change in the running preview, and Make public gives it a link for your phone or a teammate.
Set up Kai Code Bridge

Where it starts.

A ticket, a feature request or your phone.
Fix with Kai Code on any ticket, or open it in Claude Code, Codex or Cursor.
Choose Build with Kai on an approved request, or ask Kai PM to start the session.
Start a fix from a ticket on your phone and follow the session.

Your team stays in control.

Your team starts the work, reviews the PR and confirms the release.
By default a teammate confirms the merged fix is live. Approval starts the customer reply.
Send the customer update automatically after a delay you set, five minutes by default.
Turn the automatic message off and write the reply in the ticket.

From Kai Resolve's investigation.

Confirmed bugs arrive as coding tasks.
Kai Resolve investigates the ticket and files a coding task with the evidence attached. A teammate picks it up and Kai Code starts from the findings.
Meet Kai Resolve

Apps built with AI, too.

Lovable, Replit, v0 and Base44.
No repository needed. Kai Code connects through the platform's official MCP server or API, asks its agent for the fix and publishes if your team allows it. Gleap follows up with the customer once it's live.
Gleap for vibe-coded apps
What teams say about Gleap
“Everything is in the same place.”
Tridonic brought customer interactions, ticket routing, surveys, AI support, and product guidance into Gleap. The team uses one dashboard to manage its customer communication.
Elif Kavas
Digital Customer Experience Platforms Specialist, Tridonic
“Gleap has everything in one place; that is the biggest benefit.”
Salesforge moved support, roadmap requests and product news into one workspace for the whole company, developers included.
Pratham "Patrick" Mittal
Salesforge
About Kai Code
What is Kai Code?
Kai Code is Gleap's AI coding agent: it turns a ticket, bug report or approved feature request into a planned change, code and a pull request your engineers review. Gleap keeps the session, the diff and the pull request in the ticket and follows up with the customer based on your release settings.
How is Kai Code different from Claude Code, Codex or Cursor?
Claude Code, Codex and Cursor are general-purpose coding agents. Kai Code is the AI coding agent built into Gleap's support workflow: it starts from a customer ticket or an approved feature request with the conversation attached, plus Kai Resolve's findings when the task comes from an investigation, opens the pull request in the ticket, and the customer update follows your release settings. You do not have to choose between them: Kai Code Bridge runs sessions on your own Claude Code, Codex or Cursor login, and a deep link opens any ticket in those tools. For a side-by-side view, see AI coding agents compared.
What should we give Kai Code to start?
A ticket, feature request or task description, the expected outcome and access to the repository. Gleap adds the customer conversation, device details and attachments such as the screenshot, and a coding task from Kai Resolve carries its findings from the logs and the code. Project-level instructions apply to every session.
What is the difference between Kai Code Cloud, Kai Code Bridge and deep links?
Kai Code Cloud runs the session in Gleap's hosted environment. Kai Code Bridge runs it on your own computer or server with your Claude Code, Codex or Cursor login, paired with a device code. A deep link opens the ticket in Claude Code, Codex or Cursor, and the tool reports progress back through the Gleap MCP server.
Can I use my existing Claude Code, Codex or Cursor subscription?
Yes. Pair your machine with Kai Code Bridge and sessions run on your own Claude Code, Codex or Cursor login. Your provider's limits apply, and Gleap does not bill those sessions.
Can I open a ticket in Claude Code, Codex or Cursor?
Yes, on plans with Kai Code. Choose the tool in the ticket's Fix with Kai Code menu. The deep link carries the ticket and the coding session, and the tool reports investigating, fixing and PR opened back to the ticket over the Gleap MCP server.
How does the branch preview work?
On a Kai Code Bridge session, Start preview runs the pull request branch on your paired machine and opens it in your browser. If a repository has no preview setup yet, Kai Code prepares one with you the first time. Make public gives the preview an HTTPS link for your phone or a teammate; anyone with the link can open it. Kai Code Cloud sessions have no preview.
Can Kai Code check its own change?
Yes, on a Kai Code Bridge session with a preview running. Kai Code gets browser tools on its next turn and can open the running app to check the change. It is a check during the session, not a test of every behavior, and your engineers still review the diff and the pull request.
Does Kai Code require a plan before it builds?
No. Sessions on Claude and GPT models, including the default Claude Opus 5.5, build straight away and plan as part of the work. Other models offer a choice between Plan and Build. Your team starts the task, reviews the pull request and merges. Coding tasks from Kai Resolve are picked up by a teammate before the session starts.
Does Kai Code merge or deploy without our review?
No. Kai Code opens a pull request. Your engineers review, merge and deploy, with the diff and checks next to the customer context. On an app built with Lovable, Replit or v0, Kai Code publishes only if your team switches on Kai may publish for that app.
Does Kai Code work with GitLab?
Yes. Kai Code works with GitHub, GitLab, Bitbucket and Azure DevOps, and a session can span more than one repository. On Azure DevOps, Kai Code opens the pull request from Kai Code Cloud and from the Kai Code Bridge.
Does Kai Code work with Lovable, Replit, v0 and Base44?
Yes, without a repository. Kai Code connects through the platform's official MCP server or API and asks its agent to make the change in your app: Lovable, Replit, v0 or Base44. Once the change is published, Gleap follows up with the customer. See Gleap for vibe-coded apps.
Is Kai Code an AI software engineer?
For the part that ends in a pull request, yes. Kai Code plans, writes and tests code from a customer ticket and hands the result to your engineers for review. It does not merge or deploy.
When does the customer receive an update?
After the merge, following your setting. By default a teammate confirms the fix is live, then Gleap drafts and sends the reply. You can also send an automatic message after a delay, or turn it off and reply yourself. See how Gleap closes the loop.
How does Kai Code work with the other agents?
Kai Support answers customer questions. Kai Resolve investigates and files coding tasks for confirmed bugs. Kai PM recommends priorities and can start a coding session after your team approves the request and repositories. Kai Code opens the pull request. Together they run self-driving development on Gleap.
How is Kai Code billed?
Kai Code is included in Gleap Team, $149 per month billed annually ($179 billed monthly), and in Pro and Enterprise. Kai Code Cloud sessions are billed at API usage pricing, by the tokens they use; Pro adds LLM model choice. The coding in Kai Code Bridge sessions runs on your own Claude Code, Codex or Cursor login and is not billed by Gleap; starting a session needs a positive AI balance. See pricing.
Kai Resolve Second level support engineer Kai Code Software engineer
Kai Code, the AI coding agent that opens the pull request.
Start free trial
See pricing
4.6 / 5
on G2