Login
Start 14-day free trial

Self-driving development.

Customer reports become shipped fixes. Kai answers the customer, Kai Resolve investigates and returns a verdict with evidence, Kai Code opens the pull request, and the customer hears back after the release. Your team decides what ships and your engineers merge.

4.6/5 on G2
Trusted by 4,500+ teams worldwide
Start 14-day free trial
Book a demo
CSV export stops at 1,000 rows
#146960
Today
Tobias Keller9:12 AM
The CSV export stops at 1,000 rows. Our segment has 4,200 contacts, so the file is incomplete.
Kai9:12 AM
Thanks Tobias. Exports are not capped on your plan, so this looks like a bug. Kai Resolve is checking the export now and we will get back to you here.
  1. 9:13 AM
    Working · reading the export logs
  2. 9:19 AM
    Found a likely bug
    Export pagination stops after the first page: exportContacts ignores the cursor from the API response.
    Ask for changes Fix with Kai Code
  3. 9:24 AM
    Handed to Kai Codeby Lukas
GleapSDK/Desktop
  1. 9:25 AM
    Working · reading src/export/contacts.ts
  2. 9:41 AM
    Pull request opened
    #412 kai/fix-export-pagination Checks passed
  3. 1:58 PM
    Merged by Lukas
    #412 kai/fix-export-pagination Merged
Lukas
Lukas2:10 PM
The fix is live: exports now include the whole segment. Thanks for flagging it, Tobias.
ReplyNoteAsk Kai Copilot
Hey Tobias,TAB
Send
Run the loop on one ticket from your own queue.
Start 14-day free trial
Trusted by 4,500+ teams
What self-driving development is. Software development that starts from the customer report and ends when the customer hears back. AI agents carry the work between those two points; your team sets direction, decides and reviews.
Customer report
Answer & route
Investigate
Build & test
Gleap team memberGleap team memberGleap team memberReview & ship
Customer follow-up

One ticket instead of five tools.

The report, the verdict, the pull request and the reply stay together.
Before, a report became a Slack thread, a Jira issue, a branch and a status meeting while the customer waited. Now the same report is answered, investigated, fixed and closed inside one Gleap ticket.
See how the loop closes
Ticket queue
  1. Ticket
  2. Slack
  3. Jira
  4. Branch
  5. Meeting
  6. Waiting
Self-driving development
  1. Report
  2. Answer
  3. Verdict
  4. Decide
  5. Pull request
  6. Customer told

From report to verdict.

Each step has an owner and an artifact.
How do I export a segment as CSV?
Go to Contacts › Export CSV.
Exporting contacts
That worked, thanks!
Resolved by Kai
Answers from your help center and connected sources, with the article cited. What it cannot settle is routed on with the context.
Code investigation Read-only
  1. Cloning GleapSDK/Server
  2. Reading pushGate.ts
  3. Found it: pushGate.ts:142
Bug Returns early without an email.
Session replay, console and network logs, read-only code. The verdict cites file and line: answerable, bug, feature request or inconclusive.
Kai Resolve prepared a coding task
Found a likely bug
Survey pushes skip anonymous visitors: sendSurveyPush returns early without a contact email, but delivery only needs the session's subscription. Remove the guard and add a regression test.
Ask for changes Fix with Kai Code
Handed to Kai Code
Confirmed bugs arrive as a coding task with the evidence attached. A teammate hands it to Kai Code, opens it in another tool or sends it back.

From verdict to release.

Reviewed by your engineers, then back to the customer.
3 changed files +84 −12 PR #412
  • Notifications.tsx +61−9
  • useNotificationSocket.ts +19−3
  • Notifications.test.tsx +4−0
src/drawer/Notifications.tsx
  @@ -42,7 +42,15 @@ NotificationsDrawer  const { items } = useNotifications();− useEffect(() => { if (open) refetch(); });+ const socket = useNotificationSocket();+ useEffect(() => {+   if (!open) return;+   return socket.on('notification:new',+     (n) => setItems((p) => [n, ...p]));+ }, [open, socket]);  return <Drawer open={open}>
Plan, code change, tests and a pull request linked to the ticket. Runs in Gleap Cloud or on your own machine with Kai Bridge.
Starting preview
Installing dependencies…
Desktop — Web app
localhost:4200 · running on Lukas’s MacBook Pro · PR #412
Open
One-click preview of the pull request, checks and an end-to-end recording. Merging stays with your engineers.
Fix merged. Is it live?
Confirm before Rami hears back.
#412GleapSDK/Desktop
Not fixed Confirm & reply
A teammate confirms the fix is live, then the reply goes out on the original ticket. Verified, scheduled or written by hand.
Feature request
23
Working hours per teammate
Planned · Luca subscribed

Feature requests become decisions.

Demand is linked, not lost.
Reports that are not bugs are linked to the matching feature request and the customer is subscribed to updates. Kai PM scores that demand against your goals. Your team decides what gets built.
Meet Kai PM,

Your team stays in control.

Read-only investigation, approved tasks, reviewed merges.
Access for this investigation
  • GleapSDK/ServerRepository Read-only
  • GleapSDK/WidgetRepository Read-only
  • Postgres via MCPData Read-only
  • Writes, deletes, billingAny tool Blocked
Repositories are cloned into a sandbox and never written to. Destructive database and billing operations are blocked.
Fix with Kai Code
Kai Resolve proposes, a person approves. Pick Kai Code, Claude Code, Codex or Cursor, or send the task back with notes.
Verifying…
0 of 5 checks · recording
Run 6
Checks 0/5
  • Open the notifications drawer
  • Push a notification while open
  • New item appears live
  • Unread count increments
  • Works on mobile Safari
Recording 0:42 · 3 screenshots
Recording
0:42
Drawer open New item Mobile
Kai Code tests the change end to end and records the run. Your engineers review the diff and merge the pull request.
An essential part of our development process.
“Gleap was implemented within minutes and it is now an essential part of our development process.”
Mark Breuß
Founder, MARK.ONE
About self-driving development
What is self-driving development?
Self-driving development is a way of building software where AI agents carry a customer report through the answer, the investigation, the code change and the release, and the customer hears back, while your team sets direction, decides and reviews. In Gleap, Kai answers, Kai Resolve investigates, Kai Code builds, and your engineers merge.
How is self-driving development different from self-healing software?
Self-healing software is the outcome: software whose customer-reported issues are found and fixed with little manual work between report and release. Self-driving development is the workflow that produces it, including the branches that end in an answer or a product decision instead of code. Read the guide to self-healing software.
How is self-driving development different from an AI coding agent?
An AI coding agent starts from a task an engineer writes. Self-driving development starts from the customer: the report is answered, investigated and turned into a verdict with evidence before a coding task exists, and the customer is told when the fix ships. Kai Code is the AI coding agent inside that loop; it also opens tickets in Claude Code, Codex or Cursor.
How is self-driving development different from AI customer support?
AI customer support ends at the answer. Self-driving development continues when the answer is not enough: the ticket is investigated against the session, the logs and the code, confirmed bugs become pull requests, and the reply comes after the release. Kai is the AI support agent that starts the loop.
Which agents run the loop?
Kai answers customer questions and brings the team in when needed. Kai Resolve investigates hard tickets and returns a verdict with evidence. Kai Code turns approved work into plans, code changes and pull requests. Kai PM helps triage and prioritize feature requests. All of them work inside the same Gleap ticket.
Does AI change our code without review?
No. Kai Resolve reads code in a read-only sandbox and never writes to it. Kai Code opens a pull request that your engineers review and merge; coding tasks proposed by Kai Resolve need a teammate's approval before a session starts. Merging and deploying stay with your team.
What happens when a report is not a bug?
It still gets an ending. A setting or expected behavior gets a grounded reply. A feature request is linked to the existing request and the customer is subscribed to updates. An open question goes to your team as a card with options. Close the loop shows each branch.
When does the customer hear back?
After the fix is live, on the original ticket. By default a teammate confirms the merged change is live and the reply goes out; you can schedule the message after a configured delay or write it yourself. A merged pull request alone never triggers a customer message.
What does self-driving development need access to?
The ticket and what the Gleap SDK captured: device and SDK versions, console and network logs, session replay and screenshots. You choose which repositories Kai Resolve may clone read-only, which data sources it may query, and where Kai Code runs: Gleap Cloud or your own machine through Kai Bridge. See the Trust Center.
Is this AI-driven software maintenance?
Yes. AI-driven software maintenance is the part of self-driving development that handles bugs and regressions reported by customers: the report is reproduced from the session and the code, confirmed bugs become coding tasks, and the fix ships as a reviewed pull request. Feature work and product decisions follow the same loop through Kai PM.
What is agentic development, and how does Gleap do it?
Agentic development means AI agents plan and carry out development work end to end instead of suggesting the next line. Gleap connects that work to the customer: the agents share one ticket, hand over with evidence, and stop at every consequential step for your team. Kai Code is the agent that builds.
Where should a team start?
With one ticket. Turn on bug triage so new reports from in-app bug reporting arrive investigated, review the first verdict, and hand one confirmed bug to Kai Code. Extend to escalations from Kai once the verdicts hold up.
Which plan includes self-driving development?
Kai Resolve and Kai Code are included in Gleap Pro; Kai is in every plan. AI usage is billed separately by tokens and model. See pricing for details.
Customer reports become shipped fixes. Your team decides what ships.
Start 14-day free trial
See pricing
4.6/5
on G2