Kitsoki docs
Use this page as a reading path, not as a sitemap. If you are new, answer the evaluator questions in order; if you already know what you need, use the collapsed sidebar or search for the full allowlisted docs inventory.
Decide if Kitsoki fits
- Evaluate Kitsoki explains the control-inversion claim and compares it with coding agents, orchestration frameworks, durable workflow engines, and scripts.
- Proof path gives the short demo sequence: runtime guardrails, trace replay, operator handoff, and real repo workflows.
- Concept is the architecture thesis behind progressive determinism.
Understand the architecture
- Architecture is the organized map of the engine, runtime boundaries, agent surfaces, integrations, and project infrastructure.
- System map shows the package layers, turn loop, LLM boundary, persistence model, and trust model.
- MCP Studio is the external-agent facade for authoring, driving, testing, and inspecting Kitsoki without live LLM spend by default.
Try it locally
- Getting started is the shortest path from a downloaded binary to
onboard .in an existing repo. - Download Kitsoki lists release artifacts and checksums.
- GitHub App setup covers tighter repo-scoped GitHub auth when the local
ghpath is not enough.
Build or change a story
- Stories introduces rooms, intents, guards, transitions, and effects.
- Authoring Guide is the practical story-writing guide.
- Recipe: add an intent is the smallest useful edit path.
- Recipe: deterministic flow test shows how to cover a story without live LLM spend.
Test, replay, and debug
- Testing explains flow fixtures and host cassettes.
- Kitsoki JSONL Trace Format documents the audit trail.
- Run-status web UI covers trace inspection and replay surfaces.
- MCP studio lets external agents author, drive, test, and inspect Kitsoki through one facade.
Browse by area
The sidebar contains the full docs inventory, collapsed by section so this page stays readable. These section starts are the useful broad entries: