Open the board
A project board for you and your coding agents

Finish the apps you almost shipped.

Describe a feature in one sentence. Klio writes the stories, your coding agent builds them by ID, and every project reopens where you stopped.

Open the board Read the setup guide
Works with Claude Code, Cursor, Codex, Windsurf and VS Code through MCP. No files to export.
klio.dev/app/p/poc/boardOpen the board →
Hands work to
Why Klio

Vibecoding is fast. Coming back to a project is slow.

You build in bursts, switch apps when a new idea hits, and lose the thread. Klio keeps the thread for every project you start.

Without Klio 3 projects · 1 memory
  1. Login flow 80% done on feature/login. Wrong-password state left.
  2. New idea: an AI journaling app. Opens a fresh repo.
  3. Study group asks for a Discord bot. Two evenings gone.
  4. Back to the first app. Which branch? Which prompt? Was Resend ever set up in production?
  5. Twenty minutes of digging before a single line of code.
With Klio opens on this
Away 21 days · you stopped here

POC-33 Login form and session handling

Next
Wrong password shows a generic inline error
Files
app/(auth)/login/page.tsx
Stack
Supabase Auth · Resend key missing in preview
Then
POC-34 Email verification · POC-36 Route guard
Continue POC-33Copy resume prompt
01 AI planning

One sentence in. A scoped feature out.

Klio reads the project's stack and existing features, then writes small stories your agent can finish one at a time.

  • Acceptance criteria on every story, so done means done
  • Likely files and the services each story touches
  • You review and untick before anything lands on the board
↵

Agent-ready
02 Resume

Every project opens where you left it.

A bookmark for each project: the story in progress, the criteria still open, your last note, and what comes after. One tap copies all of it as a prompt.

  • All projects on one screen, with how long each has been idle
  • AI rewrites a messy note into the next concrete step
All projects · 3by last session
Pocketbook 52%POC-9 · Parse receipt totals from OCR response
today
Lumen 56%LUM-9 · Streak counter uses local midnight
idle 6d
Tidepool 36%TID-5 · Question bank JSON format
idle 19d
03 Stack tracking

Know what every project runs on.

Frameworks, databases, hosting, email, payments, AI APIs, domains and the tools you build with. Paste a package.json and Klio fills most of it in.

  • Env var names per environment. Values never leave your machine.
  • Monthly spend, and the domains or plans that renew soon
  • Stories link to the services they touch
Pocketbook · 14 services$23.87 / mo
Prodpocketbook.app · Vercel
Previewgit-*.vercel.app
Locallocalhost:3000
NJ
Next.js 14.2Frontend · App Router
Active$0
SU
Supabase Postgres 15Database · 3/3 env vars in prod
Active$0
GC
Google Cloud VisionVISION_API_KEY missing in production
Check$3.00
RE
ResendEmail · planned for POC-F4
Planned$0
PO
pocketbook.appDomain · renews in 23 days
Renews$10.44/yr
04 Agent connection

Your agent reads the board. You say the number.

Klio runs an MCP server. Connect Claude Code, Cursor, Codex, Windsurf or VS Code once with a token, and build POC-F4 is the whole prompt. No Markdown files to export or keep in sync.

  • Agents mark stories in progress, tick criteria and post summaries while they work
  • Finishing a story rewrites your "where I stopped" note for you
  • GitHub PRs that mention POC-33 move it to review, merges move it to done
$ claude mcp add --transport http klio https://klio.dev/api/mcp \ --header "Authorization: Bearer klio_…" › build POC-F4 ● klio.get_feature POC-F4 → 6 stories, 19 pt ● klio.start_issue POC-31 · In Progress ● klio.check_criterion POC-31 #1 · 1/3 ● RESEND_API_KEY missing in preview · noted ● klio.complete_issue POC-31 → In Review next up: POC-32 Sign-up form with validation
The loop

From idea to shipped, without losing the thread.

1

Start a project

Name it, pick a starter stack or paste package.json.

Pocketbook · Next.js + Supabase
2

Describe a feature

AI splits it into stories with criteria and files.

“Add login with email”
3

Hand it off

Your agent reads it over MCP and builds by ID.

› build POC-F4
4

Come back anytime

The project opens on the story you were in.

Continue POC-33 · 80%
Also in the box

A full issue tracker,
minus the ceremony.

The story, the agent, the proof, the next step. One shared place to keep the work moving.

Every story carries its context.

Acceptance criteria, agent claims, review notes and human handoffs stay with the work. Track environment variable names without storing secrets.

Explore the MCP tools
FAQ

Questions builders ask.

Does Klio see my code?

No. Klio only keeps what you type into it: projects, stories, notes, service names and env var names. Your coding agent reads your code locally, the way it already does.

Where do my env var values go?

Nowhere. Klio tracks variable names and which environments have them set. If you paste KEY=value, the value is dropped before it's saved.

Do I have to export Markdown files for my agent?

No. Klio is an MCP server, so Claude Code, Cursor, Codex, Windsurf and VS Code read and update the board directly. One CLI command sets it up per repo. KLIO.md export is still there for agents that can only read files.

Which AI writes the stories?

Your choice. Klio AI runs on OpenRouter, or bring any OpenAI-compatible key (OpenAI, OpenRouter, Groq, a local model). Or switch Klio's model off and let your coding agent plan through MCP with its own model. Either way you review the stories before they land.

Why the name?

Clio was the Greek muse of history. Klio keeps the history of each project so you don't have to.