continuity
[Alpha] Shared presence, file-activity awareness, decisions, task claims & handoffs for parallel Claude Code sessions. Works locally (SQLite, zero-config) or against a team server.
Plugin continuity from marketplace continuity in uziiuzair/continuity-mcp. Commands read from the repo's manifest — 11 days ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use and it starts local MCP servers. The exact commands are listed below; read them before installing.
What it installs
Skills (6)
coordinationCoordinate with other Claude Code sessions working on this project in parallel. Use at the start of substantive work, and before editing a file, to check who else is active and which files other sessions are touching — so you don't duplicate work or collide. Also use to advertise what you're working
decisionsRecord and read shared decisions (architecture, tooling, process, scope) so parallel Claude Code sessions stay consistent. Use when you make a call other sessions must respect, when you hit a decision another session already made, or to resolve a decision conflict.
handoffsHand off work between Claude Code sessions (or to a human), and pick up handoffs left for you. Use when you're stopping mid-task, when work belongs in another session's lane, or at task start to check whether a pending handoff already covers what you're about to do.
loopThe Continuity Loop - keep checking in with sibling Claude Code sessions on a self-backing-off schedule. Use when there are other active sessions in this repo, when you are working in parallel with sibling sessions, to start the Continuity Loop, or when a prompt begins with a `[continuity-loop]` tic
startStart the Continuity Loop now: announce your task, worktree and path to sibling sessions in this repo, and check Continuity on a self-backing-off schedule.
tasksClaim a task or issue before working on it so other Claude Code sessions don't duplicate the work. Use when you begin substantive work tied to an issue — claim it first, update its status as you go, and complete or release it when done.
MCP servers (1)
continuityruns: node ${CLAUDE_PLUGIN_ROOT}/mcp/launch.mjs
Hooks (10)
- SessionStart
node
- SessionEnd
node
- UserPromptSubmit
node
- CwdChanged
node
- TaskCreated
node
- TaskCompleted
node
- PreToolUse
node
- Stop
node
- PostToolUse
node
- PostToolUse
node
Maintain continuity?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.