Not every app lives in a git repository. If your app is built on Lovable, Replit, v0 or Base44, connect your account there and Kai Code works on the app through the platform itself: it asks the platform's own agent to make the change, checks the result and, if you allow it, publishes the app. There is no branch and no pull request; your team decides what goes live.
Ticket → Kai Code session → Platform agent changes the app → Publish → Customer reply
What Kai can do on each platform
Platform | Kai works on a | How the change is made | Kai can read the code | Publishing |
|---|---|---|---|---|
Lovable | project | Kai asks Lovable's agent and reads the diff it produced | Yes | Kai can publish |
Replit | app | Kai asks Replit Agent; it can ask Agent how the app works first | No | Kai can publish |
v0 | chat | Kai sends the change as a message in the chat | Yes | Kai can publish (deploys to Vercel) |
Base44 | app | Kai asks Base44's editor AI, or edits the files itself in the app's sandbox (it creates a checkpoint first) | Yes | Kai can publish |
Kai can publish only where you turn on Kai may publish for the app. See Publishing.
Connect a platform account
- Open the Vibe coding settings
Go to AI agents → Kai Code → Settings → Vibe coding. Every supported platform is listed with a short line on what Kai can do there.
- Connect
Choose Connect next to the platform. A popup opens the platform's sign-in; sign in and approve Gleap's access. Base44 asks for a personal access token instead: see Connect Base44. The connection appears as Connected with Connected by and your name.
- Add the apps Kai may work on
Choose Add app (Add project on Lovable, Add chat on v0). Gleap lists what your account can reach on the platform; search and pick one to link it to the project. Repeat for every app Kai should work on.
Connect Base44
Base44 connects through its official API with a personal access token rather than a sign-in popup.
In Base44, click your workspace name at the bottom left, then Settings → Secrets → Personal access tokens → Create access token.
Under Access, choose the apps Kai should work on (or all apps). Under Permission, choose Full access: a read-only token cannot change or publish anything.
Copy the token, choose Connect next to Base44 in Gleap and paste it. Gleap checks it with Base44 before saving it.
Add the apps. Base44 lists the apps in your personal workspace; for an app in a team workspace, paste its Base44 editor link into the search field.
Base44 needs a Builder plan or higher for this. A token belongs to one Base44 workspace and stops working if you leave it or an admin switches it off; the connection then shows Expired and you paste a new token.
A connection is one teammate's platform account. Everything Kai does on the platform runs as that person, with their account's plan and limits on the platform. The sign-in tokens stay on Gleap's servers; Kai never sees them.
Who can manage a connection
Teammates with access to the Kai Code settings can see every connection and its linked apps. Because a connection acts as someone's personal account, only the teammate who connected it, or an admin of the project or organization, can:
add apps through it,
turn Kai may publish on or off for its apps,
reconnect or disconnect it.
Other teammates can start Kai Code sessions on the apps that are already linked.
Expired connections
If the platform signs Gleap out (or Base44 refuses the token), the connection shows Expired with the reason. The teammate who connected it chooses Reconnect and signs in again, or pastes a new token on Base44; the linked apps stay linked.
Disconnect or remove an app
Remove on an app's row takes it out of the project. Kai Code can no longer pick it; you can add it again later.
Disconnect in a connection's menu ends the connection and removes all of its apps from the project. The apps themselves stay on the platform.
Fix a ticket in a platform app
Linked apps show up in the Kai Code composer's repository picker, next to your repositories. Pick an app (on its own or together with repositories) and send, or use Fix with Kai Code on a ticket. With Repos: Auto in a project that has no repositories and exactly one linked app, Kai uses that app.
Kai then works like this:
It reads the ticket: the conversation, logs and screenshots.
Where the platform allows, it reads the app's code. On Replit it asks Replit Agent how the feature works instead.
It sends the platform's agent one focused instruction per problem, with the reproduction steps, the expected behaviour, the evidence and what must stay unchanged. Customer names, emails and other personal data are left out.
It waits for the platform to finish, checks the result (the diff or the files where it can read them) and asks for a follow-up change if something is still off. On Base44 it can also correct the code itself.
It publishes when allowed, or tells you the change is ready to publish.
Each step shows up in the session and on the ticket's Kai Code card, for example Asked Lovable to change Shop or Published Shop to with the live URL. The app row in the session links to the live app and to the app in the platform's editor.
Kai only reaches the apps linked to the session, and only through a fixed set of the platform's tools that act on that one app. Account settings, other apps, deleting anything and your app's end-user data are out of its reach.
Publishing
Kai may publish
Each linked app has a Kai may publish switch. It is off by default.
On: once Kai has verified the fix, it publishes the app and waits for the platform to confirm the new version is live. Only a confirmed publish counts. If publishing fails, Kai says why and the ticket stays open. Lovable refuses to publish while a project has critical security findings.
Off: Kai finishes by saying the change is ready. A teammate publishes it in the platform.
On Base44, if the token's owner may not publish the app, Kai asks Base44 to send a publish request to the workspace's owners and admins instead. The change goes live, and counts as published in Gleap, once one of them publishes it.
Manual publishing
Whenever a finished session has a change that nobody has confirmed as live (with Kai may publish off, or a publish Gleap cannot see), the app row in the session offers Mark as published. Publish in the platform first, then choose Mark as published so Gleap knows the change is live.
When the change is live
A session is done once every app it changed has been published since its last change, either by Kai (confirmed by the platform) or marked as published by a teammate. The session then posts The change is live with the URL.
From here it works like a merged pull request: your Customer replies setting decides whether a teammate verifies first or Kai replies after the deployment delay. The ticket closes once the customer has been told about the fix. If the session also opened pull requests in your repositories, it waits until those are merged too.
Install the Gleap widget with Kai Code
Kai Code can add the Gleap widget to an app built on these platforms. On the widget installation page choose Install with Kai Code, or, during onboarding, Built with Replit, Lovable, Base44 or v0?. Connect the platform, pick the app and start.
Kai installs the widget once, with your project's API key, and changes nothing else. It follows each platform's stack:
Platform | Where the widget goes |
|---|---|
Lovable | The |
Replit | The |
v0 | The |
Base44 | The loader snippet in the |
The widget only reports from the published app. Where Kai may publish is on, Kai publishes and then checks that the widget reports from the live URL. The check succeeds once someone opens the live app, so open the URL once if Kai says it is not confirmed yet. With publishing off, publish the app in the platform to finish the install.
Requirements
The Kai Code plan feature and the Kai Code permissions described in the overview.
An account on the platform with access to the app. Changes made by the platform's agent run on that account and use its credits. Base44 needs a Builder plan or higher.
Sessions on platform apps are billed like any other Kai Code session: Kai Code Cloud is billed at API usage pricing (see Plans and AI pricing), Kai Code Bridge is not billed by Gleap.