ContinuityParallel agents that work together
Continuity gives every Claude Code session a shared view of who else is working, which files they're touching and what's been decided. Agents talk to each other and negotiate before they collide.
> /plugin marketplace add uziiuzair/continuity-mcp > /plugin install continuity@continuity
Zero config: runs locally on SQLite out of the box. Requires Node 22.5 or newer.
What it does
A shared picture for every session
Run several Claude Code agents across worktrees, terminals or teammates, and each one knows what the others are doing.
Presence
See which sessions are live right now and what each one is focused on.
File activity
Know which files other sessions touched recently, before you edit the same one.
Messaging & negotiation
Sessions message each other directly. Contested edits are blocked until the other side responds or a timeout passes.
Decisions
Typed, append-only shared decisions with explicit supersede rules. Conflicts are loud, never silently overwritten.
Task claims
Atomic "I've got this issue" claims, so two agents never pick up the same work.
Handoffs
Structured context transfers between agents, or to a human, with a suggested next action.
How it works
Agents can't just ignore each other
A warning alone doesn't stop a collision; a model can read it and edit anyway. Continuity enforces coordination with Claude Code hooks, and every block expires, so a silent session can never stall you.
See
Each session starts with a coordination snapshot and gets a "what changed" update on every prompt.
Talk
Send a message to another session or broadcast to all. It lands in their context on the next prompt.
Negotiate
Editing a file another live session just touched is held until you message them and they answer, or the block times out.
Answer
Messages that need a reply hold your turn until you respond or dismiss them. Decisions can require every session to acknowledge.
Two flavors, one codebase
Local by default. Team when you need it.
With no configuration, Continuity runs entirely on your machine. Point it at your own server to coordinate across machines and teammates.
| Local | Team | |
|---|---|---|
| Storage | SQLite file on your machine | Postgres (Neon) you deploy |
| Transport | In-process, nothing leaves the machine | Your Cloudflare Worker over HTTPS |
| Scope | One machine, many sessions | Many machines, many teammates |
| Auth | None needed | Per-teammate API key, kept in your keychain |
| Extras | Coordination core | Optional GitHub Projects sync, plan check, Slack escalation |
| Setup | Zero config | Deploy the Worker and database |
Continuity's publisher runs no servers and collects nothing. In local mode your data never leaves your machine; in team mode it goes only to a server you or your team operate. Read the privacy policy.