Kairoku
Kairoku playbook
The project, release, and document workspace built for working with AI agents.
Kairoku keeps a project's plans, specs, and records in one governed workspace.
Your first five minutes
You do not have to set anything up, and you do not have to know what to call it. Put the thing you are thinking about into Kairoku and it works out the shape with you.
Paste what's in your head. ⌘N works anywhere. Ideas, plans, half-thoughts — one box. Several at once is normal; Kairoku sorts it out with you.
Accept what the assistant proposes. You get a plan and a next step. Nothing is filed behind your back: you look at what it suggests and say yes to the parts that are right. Saying yes turns the thought into a new project — you confirm the name first — or into a feature with a draft plan inside a project you already have, each leaving a first task waiting for you, or files it as a note if that is all it needed.
Do the next thing. Connect GitHub or GitLab later to amplify. The app is useful before anything is connected, and staying unconnected costs you nothing.
Three surfaces
Kairoku is three programs. The web app at app.kairoku.io holds projects, releases, documents, the Floor, and MCP. The desktop app is where you chat with Teammates, connect Slack, browse the integration catalog, and set up the automations your machine runs — carrying its own daemon on your machine. The CLI installs a third, separate daemon on agent machines to run dispatched work. See Desktop and Orchestration.
Sections
Getting started
Create a project and meet the document tree.
Organizations
Personal and team workspaces, and what is shared inside one.
Desktop app
The desktop app and the daemon it carries — what lives here rather than in the web app.
Connections
GitHub and GitLab for the web app — signing in, picking repositories, what the app reads, and the Slack wake relay status.
Slack
Register the App, connect the daemon, grant a Teammate, and the offline wake relay.
Integration catalog
Browse and install additional curated connectors — vault token or PAT when required.
Teammates
Named chat personas on the desktop daemon — grants, binding, the Crew.
Automations
Cron, signed webhooks and forge events bound to a prompt or a recipe — what the desktop daemon runs and what the web app only stores.
Workflows
Saved playbooks and the graph builder — node kinds, validation, runs.
MCP
Connect an MCP client to your Kairoku workspace.
Plugin
The Kairoku plugin for Claude Code.
CLI
One binary that installs the plugin, provisions an agent machine and runs the daemon.
Sync
Jira and Confluence, from the app outward — coming soon on the hosted app.
Orchestration
How agent runs are dispatched to their own machines.
Glossary
Floor Team, Teammate, Crew, Agent, Playbook, Automation — and the two daemons.
Governance
The seven rules every change to Kairoku is checked against.
The shape
The shape is small and fixed. A project holds a document tree and a series of releases. A release moves through stages — idea, exploring, planning, handoff, building, shipped, or parked to one side — and carries its own box for documents: brief, PRD, specs, implementation plan, checklist, release notes, retrospective. A release's plan is phases of plan items, each with a body and test notes written before the work starts. Agents read all of it over MCP, write documents, plan structure and progress back into it, and never mint remote structure of their own.