What it does
Fix tickets
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.
Plan, then 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.
Verify visually
Kai Verify runs your app, clicks through the change and records video and screenshots as evidence. Results can be posted to the pull request.
Close the loop
After the merge, a teammate verifies or Kai replies automatically after your deployment delay, using your reply instructions.
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 at API usage pricing from your organization’s AI balance. See Plans and AI pricing.
- 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.
Apps built on Lovable, Replit, v0 and Base44
Kai Code also works on apps that live on a vibe coding platform instead of a git repository. Connect your platform account and Kai asks the platform’s own agent to make the change, then publishes it if you allow it. See Lovable, Replit, v0 and Base44.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. Apps built on Lovable, Replit, v0 or Base44 get the widget through the platform.Start here
- Getting started: the setup wizard: repository, tools, customer replies.
- Sessions: the composer, plan review, verification and pull requests.
- Tickets and pull requests: Kai Code inside the inbox.