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.
Works with Claude Code, Cursor, Codex, Windsurf and VS Code through MCP. No files to export.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.
- Login flow 80% done on
feature/login. Wrong-password state left. - New idea: an AI journaling app. Opens a fresh repo.
- Study group asks for a Discord bot. Two evenings gone.
- Back to the first app. Which branch? Which prompt? Was Resend ever set up in production?
- Twenty minutes of digging before a single line of code.
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
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
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
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
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
From idea to shipped, without losing the thread.
Start a project
Name it, pick a starter stack or paste package.json.
Pocketbook · Next.js + SupabaseDescribe a feature
AI splits it into stories with criteria and files.
“Add login with email”Hand it off
Your agent reads it over MCP and builds by ID.
› build POC-F4Come back anytime
The project opens on the story you were in.
Continue POC-33 · 80%A full issue tracker, minus the ceremony.
Board, list, features
Drag across six statuses on desktop. On a phone, flip through one status at a time.
Keyboard first
⌘K finds anything. C new issue, F new feature, P all projects, 1–6 switch views.
Environments
Production, preview and local, with host, URL and branch for each.
Teams and GitHub
Invite collaborators, and let pull requests move stories for you.
Spend at a glance
Monthly cost per project and category, yearly plans folded in.
Bring your own model
Klio AI on OpenRouter, your own OpenAI-compatible key, or let your agent plan.
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.
Where does Klio run?
On Cloudflare Workers with a D1 database. You can self-host it: deploy your own copy with one command and keep the data in your Cloudflare account.
Why the name?
Clio was the Greek muse of history. Klio keeps the history of each project so you don't have to.
Pick up the project you left last month.
Sign in with GitHub. Your workspace starts with a five-minute tour project.