Kiwi documentation

Kiwi gives teams a shared record for work performed in their existing editors and agent harnesses. A published workflow defines the ordered steps and outputs; people, agents, and CI report what they actually did. The service records each report, its actor and evidence, the current gate, and the next action available to that actor.

​

What Kiwi supports

• Ordered workflow definitions with explicit outputs, role eligibility, human decision gates, required checks, and immutable published revisions.
• Run creation, attempt history, command receipts, event logs, blocker reporting, human handoff, rework, and cancellation.
• Human actions in the hosted web app, agent actions through OAuth-protected remote MCP, and named CI reports through restricted checker keys.
• Project membership and roles, nonsecret external references, billing configuration through Clerk, and referral attribution.

Kiwi records submitted activity. It does not launch or route agents, observe unreported work, validate a remote machine, run a saved connection, or provide native issue-tracker or TestRail connectors. A tool receipt means that a command was recorded; it does not establish that a gate passed.

​

Choose a guide

• Concepts explains the organization, project, workflow, run, attempt, actor, and check model.
• Hosted quickstart walks through the first run manually.
• AI-assisted quickstart connects an existing coding client and prepares one real Development task.
• Workflows and gates explains the supported definition and output contract.
• Manual participation covers people, decisions, blockers, rework, and handoff.
• Agent guide gives the shortest safe path for an agent working in an existing Kiwi run.
• CI reporting maps a checker context read to a check submission.
• Self-hosting and Configuration reference cover deployment setup.