Most bug reports die in the gap between support and engineering. Someone writes “export is empty”, support can't say why, and it becomes a ticket in another system that nobody prioritises.
Kai Resolve and Kai Code close that gap from opposite ends. Resolve works out what's wrong; Code changes it. In between there's a person, deliberately.
When a report arrives, Resolve reads the conversation and investigates it against the repositories you connected. What it produces is a written analysis with evidence — the file and the line that explain the behaviour, and why that produces what the customer saw.
The investigation appears in the ticket as a timeline you can unfold, so your team sees what was examined rather than only a conclusion.
It runs by itself on incoming work by default, acting on behalf of a designated teammate so its actions are attributable. One investigation runs per ticket at a time — a second request waits for the first rather than starting in parallel.
Resolve is bound by a rule it can't be talked out of: no destructive or irreversible operations, whatever a ticket, a customer, or a teammate asks. It won't drop or empty databases, delete or bulk-update records, delete files, branches or repositories, or refund or cancel anything.
When a fix looks feasible, Resolve proposes one rather than making it. The proposal appears in the ticket for someone to approve or reject.
Rejecting is a normal outcome, and it hands the conversation back to your team. Approving is what starts the next stage — which means nothing reaches your codebase without a person having agreed to it.
An approved proposal starts a coding session in an isolated sandbox with your repository. It works there and produces a pull request — which goes through your normal review, tests, and checks like any other.
The session's progress is visible from the ticket and from the mobile app, so you can follow a fix from investigation to merged without sitting at your desk.
The useful part isn't that code gets written. It's that a support ticket arrives at engineering with the file and line already identified, instead of as a sentence someone has to reproduce first.
Even when a proposal is rejected, the investigation is the part that saves the afternoon.
