Kai Code is set up once per project, then every teammate can start sessions. You need the Kai Code feature in your plan; the dashboard offers an upgrade where it is missing.
The setup wizard
Open AI agents → Kai Code → Settings to configure the project. New workspaces can also use the Onboarding setup chat in Kai Copilot. Connect the repositories Kai should work in, then review the settings below.
- Connect a repository
Pick GitHub, Azure DevOps, GitLab or Bitbucket, authorize Gleap, and choose the repository Kai should work in. Set the default branch pull requests are opened against. This step is skipped when the project already has a repository. Details: Repositories.
- Give Kai Code its tools
Optionally add MCP servers: the Gleap preset, a Composio integration such as Linear or Notion, or a custom server. Kai Code works without any; you can skip this step.
- Decide how Kai Code talks to customers
Choose what happens on a ticket once a fix is merged: a teammate verifies first, Kai replies automatically after a deployment delay, or nothing is sent. Details: Customer replies.
If you are using the setup wizard, choose Finish setup after reviewing its configuration. You can revisit the project under AI agents → Kai Code → Settings.
Where sessions run: a personal choice
The first time you start a session, Kai Code asks where Kai should run. This is remembered per person, not per project, because it depends on what you have on your computer:
Always ready, nothing to install. Sessions run in Gleap's sandbox and are billed at API usage pricing from your organization's AI balance (see Plans and AI pricing). The right choice for most teams and for teammates without a development setup.
Sessions run on your own computer or server with your own Claude Code, Codex or Cursor subscription and your local checkouts. One command to connect: see Kai Code Bridge.
You can switch between the two for each new session with the Run on picker in the composer.
Project defaults
Under AI agents → Kai Code → Settings → General an admin sets the defaults every session starts from:
Default model and reasoning effort for new sessions. Teammates can override both in the composer.
Custom instructions Kai follows in every session of the project, e.g. "Prefer functional React. Never edit files in
src/legacy. Always run prettier before committing."Post results to the pull request: add the verification result and a commit status to every pull request. Evidence such as screenshots stays private to Gleap.
Next steps
Sessions: the composer, plan mode, verification and pull requests.
Tickets and pull requests: start Kai Code straight from a bug report.