Hobby
$29per month, billed yearly
For one person.
- 1 seat, 1 project
- Live chat and inbox
- In-app bug reporting
- Kai Support and Kai Copilot
You built it with Lovable. Gleap runs the support and fixes the bugs.
Kai Support answers your users, Lovable's agent fixes the bugs after one click from you, and the user hears back.
7 days free. No credit card needed.
Sofia Lindqvist
Mia Kellerman
Jonas Weber
Tom Alvarez Tomorrow
Ade Okafor
Priya Raman
Florian Berger
Kai Support handed the conversation to the team
Trusted by 4,500+ teams
Kai Support replies in the chat widget inside your Lovable app, and by email.
After one click from you, in the project you already edit.
A failed request to your Supabase backend arrives with the bug report.
Kai may publish is off until you switch it on for a project.
On autopilot
Gleap for Lovable is an integration that adds AI customer support and bug fixing to the app you built with Lovable. Kai Code reads the project through Lovable's official MCP server, describes the fix to Lovable's agent and reads the diff. It can't write your code. Connecting Lovable needs Growth, at $99 a month billed annually.
I’ll find why the picker closes, then ask Lovable to make the change.
The picker closes on blur, and Safari blurs the input before the day click lands.
The picker now stays open until a day is picked. Publishing it now.
The change is live: https://lumen-demo.lovable.app.
Kai Code finds the cause in your Lovable project.
In words, to Lovable's agent.
Against what the ticket needs.
Lovable's agent makes every change.
What runs without you
When a user describes something broken, Kai Support files the bug with the session attached. Console and network logs show a failed Supabase request.
Meet Kai SupportIn the chat widget inside your Lovable app and by email, from your help center and docs.
Kai Code · Merged · 2:30 PM
Once the change is published in Lovable, Gleap replies on the user's original ticket.
In Kai Code settings, open Vibe coding, connect Lovable with its own sign-in and add the projects Kai Code may work on. Kai may publish is off until you switch it on for a project.
Meet Kai CodeInstall
Kai Code asks Lovable's agent to add the gleap npm package and one Gleap.initialize call in src/main.tsx, and changes nothing else.
Read the docsPricing
$29per month, billed yearly
For one person.
$99per month, billed yearly
For a support team on every channel.
$299per month, billed yearly
Everything in Growth, plus control.
7-day free trial. No credit card needed.Compare all features
Questions
Gleap for Lovable is AI customer support and bug fixing for the app you built with Lovable. Kai Support answers your users around the clock from your docs, bug reports arrive with a screenshot, replay and logs, and Kai Code asks Lovable's agent for the fix. Once it's live, Gleap replies to the user who reported it.
Every plan starts with a 7-day free trial, and no credit card is needed. See pricing.
Start a Kai Code task and it asks Lovable's agent to install Gleap: the npm package gleap with Gleap.initialize("API_KEY") once in src/main.tsx. You can also add those two lines yourself.
The widget brings the AI chat, bug reports and your help center into the app.
Yes. Kai Support answers in the chat widget inside your Lovable app, and by email, from your help center, docs and the sources you connect.
It hands a conversation to you when it can't help or the user asks for a human, and it recognizes bug reports and files them with the session attached.
When the fix is live, Gleap writes the reply on the user's original ticket. Turn on automatic follow-up and it sends by itself, right away or after a delay you set. Otherwise a teammate confirms first with one click.
Yes. Kai Code connects to Lovable's official MCP server, and you approve access with your Lovable sign-in (OAuth). It reads files and diffs, sends change requests to Lovable's agent and, if you allow it, publishes. It can't create or delete projects.
Only if you switch on Kai may publish for that project. Otherwise your team publishes in Lovable and marks the change as published in Gleap, which starts the follow-up to the user.
Bug reports carry the browser's console and network logs, so a failed request to your Supabase backend arrives with the report, next to what the user did.
Kai Code reads the project's files to find the cause, then describes the change to Lovable's agent in words. Lovable's agent makes the change in the background.
Kai Code waits until it has finished and reads the diff to check that it does what the ticket needs.
No. Kai Code can read the files in your Lovable project but can't write them. Lovable's agent makes every change.
Yes. It uses Lovable's plan mode, which discusses the project without changing code. If plan mode isn't available, Gleap refuses the call instead of sending it as a change request.
Lovable, Replit, v0 and Base44, and code in GitHub, GitLab, Bitbucket and Azure DevOps. See Gleap for vibe-coded apps.