English | 繁體中文
koopa is a private planning and publication system — your areas, goals, projects, daily work, and publishable writing in one place, with AI agents working inside it.
The agents share one source of truth for work state: they read the same live state you do, instead of whatever you remember to tell them. You stay the only decision-maker — they inspect, draft, and propose; you decide what's kept. Knowledge authoring and retrieval stay in Obsidian／Yomihon.
You're juggling a lot — responsibilities you keep up, goals you're chasing, projects in flight, a daily list, things you're half-writing. What you want is help keeping it all moving: something that remembers where you left off, surfaces what's slipping, and works alongside you — not just another app you have to feed.
Most AI tools can't be that, because they forget. Every conversation starts from zero, and the more assistants you add, the more time you spend re-explaining yourself. koopa stores the work itself instead — your goals, projects, plans, and writing live in one place every agent can read. So an assistant can pull up your morning briefing, see what you finished yesterday, draft the next piece, and hand it back for your call, without you recapping a thing. It helps you carry the work; it never quietly takes it over.
The line that matters isn't human vs. agent — it's flow vs. decision. Agents handle the flow: they inspect current work, draft, and propose, in conversation with you. You handle the decisions: an agent can suggest a new goal or hand in a finished article, but it stays a draft until you accept it in the admin UI. They coordinate through the shared state, never by handing work to each other.
| Who | Role |
|---|---|
| You (Koopa) | The only decision-maker |
| Claude Code | Development sessions in this repo — inspection, build logs, content drafts |
| Hermes | Curates a personal Obsidian vault on a schedule |
| Codex | Development collaborator — repo work and code review |
That split is the whole point. Agents can run freely — capture a todo, draft a proposal, push an article to your review queue — precisely because the commitments stay yours. Without the gate, autonomy just floods the system with things you never chose to keep.
Planning & commitments. Your work is organized PARA + GTD style — areas, goals with milestones, projects, todos, and a daily plan. The daily plan doesn't silently roll yesterday's unfinished work forward; it resurfaces in your morning briefing, so you decide what stays.
Writing & publishing. Five kinds of content — articles, essays, build logs, TILs, and digests — move through a simple editorial flow from draft to published. An agent can hand in a finished draft and revise it after you send it back, but you're the only one who publishes.
Shared context. Agents read your current planning state through MCP — goals, projects, todos, and the daily plan. Koopa does not copy or search your knowledge base; knowledge authoring and retrieval stay in Obsidian／Yomihon.
One history. Every change records who made it, so the whole system keeps a single, trustworthy timeline of what happened and when.
This is a single-admin system by design: one person, several AI agents — no team accounts, no roles, no "share with a colleague." The admin side is private; only some content (articles, build logs, TILs) reaches the public site, and only after you publish it. Goals and private notes stay private. Koopa stores planning state and publishes selected writing; the private knowledge base lives in Obsidian. If you want a team wiki or a Notion clone, this isn't it.
All Rights Reserved — see LICENSE.