Set up Klio with your coding agent.
Two minutes, once. Your agent connects to Klio over MCP, puts this repo on the board, and from then on “build POC-F4” is the whole prompt.
Connect your agent
Klio is a remote MCP server at https://klio.dev/api/mcp with bearer-token auth. Pick your editor for the exact setup.
Paste one prompt
Once your agent is connected, paste this and replace the highlighted part with what you're building. It checks the connection, puts the repo on the board, plans the work with you and builds it one story at a time.
Use Klio (klio.dev) as the project board for this repo. It's connected over MCP as "klio". 1. Call whoami to check the connection. If it fails, stop and tell me what to fix. 2. Find this repo's project with list_projects. If there isn't one, create it with create_project: name it after the repo and pick a short key. 3. Record what's already here: call sync_stack with package.json (and any other manifests), add features that already work as done stories, and half-finished work as stories in progress. 4. What I'm building next: <describe it in a sentence or two> Call brief_feature, write small stories with acceptance criteria, show me the plan, and save it with create_feature once I approve. 5. Build it one story at a time: start_issue before you write code, check_criterion as each criterion really passes, complete_issue with a short summary once it's tested. Don't start a second story while one is in progress, and leave Done to me. 6. Before you stop, hand me anything only I can do (secrets, DNS, billing) with flag_for_human.
After that, just say the number
Every session after the first starts with one line. Use your own project key in place of POC.
What should I work on in POC?Reads the board and picks the next story nobody else holds.Build POC-F4Loads the feature and works through its stories in order.Continue POC-33Picks a story back up with its criteria, files and your last note.Plan: export expenses to CSVDrafts a feature with stories for you to approve.Resume POCCatches up on where you stopped, then asks what's next.How agents move a story
Stories move in order, one at a time, as the work happens. Klio enforces it: an agent can't skip stages, start a second story while one is in progress, or mark work Done without you.
get_next_workThe agent picks the next story nobody else holds.
start_issueIt claims the story before writing code.
check_criterionEach criterion is ticked when it really passes.
complete_issueA short summary, then it's yours to approve.
Questions
Where do I get a token?
In Klio, open Settings → Connect agents and create one. Klio shows it once. Give each machine or agent its own token so the activity feed says who did what.
Does Klio see my code?
No. Your agent reads your code locally. Klio stores what you and your agent write to it: stories, notes, service names and env var names. Never values.
Can several agents share a board?
Yes. Each connection claims the story it starts, so other agents skip it. See running several agents.
My agent only supports stdio.
Use the Klio CLI as a bridge. See Any MCP client.