open source · local-first · MIT
Run many AI coding sessions without losing the thread. Each project keeps its memory through compaction: the plan, the decisions, what is left. And one lead session hears from all the others, so you watch one window instead of five.
uvx missioncache-install
LEAD3 noticesClick a session to send the lead a notice.
The lead, hooks, dashboard, statusline, autonomous runs and all 51 MCP tools.
The project files, the slash commands and all 51 MCP tools.
The project files, the slash commands and all 51 MCP tools.
The project files and all 51 MCP tools, in Copilot Chat.
Run /missioncache:lead in any Claude Code session. It becomes the lead: the one place that knows what every other session is doing.
Every project is three plain markdown files under ~/.missioncache/. Watch what happens to them from start to finish.
plan.mdThe approach you agreed on. Locked once approved.
context.mdDecisions, gotchas, key files, next steps. A living document.
tasks.mdThe checklist with progress. Any tool can tick it.
A local dashboard at localhost:8787. It reads the same project files, so there is nothing extra to keep up to date. Click any screen to enlarge it.
Installed into Claude Code's statusline. Project and progress, git, model, context use, your session and weekly limits, and whether Claude itself is having a bad day. Links open the dashboard on that project.
1
2
3
4
Every tool in this space does one thing well. Here is the whole picture, misses included.
| Capability | MissionCache | Taskmaster AI | claude-mem | GSD | Agent Teams |
|---|---|---|---|---|---|
| Project state that survives compaction | ✓ | ~ | ~ | ~ | ~task list only |
| One lead session across parallel sessions | ✓ | – | – | – | ~lead inside one team |
| Shared memory across parallel projects | ✓ | ~tags isolate lanes | ~global memory | – | – |
| Task checklists + dependency DAG | ✓ | ✓ | – | ~ | ~flat list |
| Per-project time tracking | ✓ | – | – | ~cost only | – |
| Local analytics dashboard | ✓ | – | ~ | – | – |
| Autonomous execution | ✓ | – | – | ✓ | ✓ |
| Whole project moves between tools | ✓plan + tasks + progress | ~tasks only, 13 IDEs | ~memory only, 7+ agents | – | – |
A wizard asks which parts you want and which AI tools to register. Needs Python 3.11+. The uvx command comes with uv.
uvx missioncache-installUse --all --yes for a hands-off run. pipx run missioncache-install works too.
Optional on macOS: panels for iTerm2 with --iterm-panels.
/plugin marketplace add missioncache/missioncacheInside Claude Code, then /plugin install missioncache@missioncache. No dashboard or statusline.
CLAUDE.md is a static rules file you maintain by hand. MissionCache keeps living project state (the plan, your decisions, the gotchas, progress) that updates as you work and reloads with one command. It complements CLAUDE.md, it does not replace it.
It runs a brief across every project, then receives a one-line notice whenever another session changes a project. If you want, it refreshes the brief on a schedule you pick, and it stops at the end of the window you set (7 hours by default). It never starts that loop on its own. It needs Claude Code, because it relies on cross-session messaging.
Yes. Every write waits on the project's lock and lands in one piece, so two sessions never corrupt the context file or overwrite each other. When one session changes the project, the others are told. Each session keeps its own reasoning. The project files are what they share.
On your machine. Project files are plain markdown under ~/.missioncache/, and the dashboard listens on 127.0.0.1 only. There is no account and no MissionCache server.
Claude Code gets everything: the lead, hooks, dashboard, statusline and autonomous runs. Codex, OpenCode and VSCode Copilot Chat get the project files, the slash commands and every MCP tool. Start a project in one and pick it up in another.
claude-mem recalls memories into whatever agent you are in. MissionCache moves the whole project: the plan you approved, the tasks with their progress, the decisions and gotchas, as files any MCP agent reads and writes. If you want long-lived memory across projects, claude-mem is genuinely good at that.
It keeps a summary, and every summary drops details: an edge case, a constraint, a “don’t do X”. Anthropic calls this goal drift. MissionCache keeps the plan, the decisions and the next step in files, so a session reloads them in full instead of trusting the summary.
Yes, on native Windows with no WSL. The hooks run, including the compaction snapshot, and the dashboard starts at logon. It needs Claude Code 2.1.139 or newer. A Windows CI job tests all of this on every push.
Yes and yes. It is open source under the MIT license. To remove it, uninstall the packages and delete ~/.missioncache. Your projects are plain markdown, so anything you want to keep, you keep.
uvx missioncache-install