By uziiuzair
[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.
Coordinate 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 on.
Record 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.
Hand 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.
Claim 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.
Admin access level
Server config contains admin-level keywords
Modifies files
Hook triggers on file write and edit operations
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
This plugin requires configuration values that are prompted when the plugin is enabled. Sensitive values are stored in your system keychain.
apiKeyYour API key for the team server. Required only for team mode; leave blank for local mode.
${user_config.apiKey}apiUrlBase URL of a Continuity team server (the Cloudflare Worker). Leave blank to run locally against a SQLite file — no server needed.
${user_config.apiUrl}dbPathWhere the local SQLite file lives. Defaults to ~/.continuity/continuity.db. Ignored in team mode.
${user_config.dbPath}repoAllowlistRestrict Continuity to specific repos. Leave blank to activate in any git repo.
${user_config.repoAllowlist}Requires secrets
Needs API keys or credentials to function
Requires secrets
Needs API keys or credentials to function
⚠️ Alpha. This is an early alpha release (
0.1.0-alpha.1). Everything here — the local and team flavors, the schema, the plugin, and the tool surface — is unstable and may change without notice. Expect rough edges and breaking changes; not yet recommended for production-critical workflows.
Coordination for parallel Claude Code sessions. When you run more than one Claude Code agent at once — across worktrees, terminals, or teammates — Continuity gives every session a shared view of:
Conflicts are loud, not silent: when two agents disagree (same decision key, same issue), the API returns a conflict instead of overwriting.
| Local | Team | |
|---|---|---|
| Storage | SQLite file on your machine | Neon Postgres |
| Transport | in-process | Cloudflare Worker (HTTPS + API key) |
| Scope | one machine, many sessions | many machines, many teammates |
| Auth | none (single implicit user) | per-teammate API key |
| Extras | coordination core only | + GitHub Projects, plan-check, Slack escalation |
| Setup | zero config | deploy a Worker + Neon |
The Claude Code plugin picks the flavor automatically: if you provide an API URL and
key it runs in team mode; otherwise it runs local against
~/.continuity/continuity.db.
In Claude Code, add this repo as a plugin marketplace and install the plugin:
/plugin marketplace add uziiuzair/continuity-mcp # or a local path to this repo
/plugin install continuity@continuity
With no configuration it runs in local mode (SQLite, zero-config). For
team mode, set the plugin's apiUrl + apiKey to your deployed Worker.
Requires Node ≥ 22. The local flavor uses Node's built-in
node:sqlite(no native dependencies — the plugin bundle is pure JS and cross-platform). The launcher passes--experimental-sqlite, which is required on Node 22.x–23.x and a no-op on Node 24+.
ContinuityBackend seam, the data model🚧 Early development. See IMPLEMENTATION_PLAN.md for the
architecture and build phases.
Node version: Node ≥ 22 for both flavors — the local flavor uses
node:sqlite (Node 22+), and the team flavor's Wrangler 4 tooling also needs Node 22+.
packages/shared @continuity/shared — schema, types, the ContinuityBackend interface, query logic
packages/mcp @continuity/mcp — the MCP server (local + remote backends) and plugin payload
packages/server @continuity/server — the Cloudflare Worker (team flavor)
plugin/ the Claude Code plugin (hooks, skills, .mcp.json)
docs/ architecture, local-mode, team-mode, examples
pnpm install
pnpm -r typecheck
pnpm -r build
Requires Node ≥ 22 and pnpm 9.
MIT — see LICENSE.
npx claudepluginhub uziiuzair/continuity-mcp --plugin continuityPermanent coding companion for Claude Code — survives any update. MCP-based terminal pet with ASCII art, stats, reactions, and personality.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
A growing collection of Claude-compatible academic workflow bundles. Covers scientific figures, manuscript writing and polishing, reviewer assessment, citation retrieval, data availability, paper reading, literature search, response letters, paper-to-PPTX conversion, and evidence-grounded Chinese invention patent drafting. Rules are organized as reusable skill folders with explicit workflows and quality checks.
Complete creative writing suite with 10 specialized agents covering the full writing process: research gathering, character development, story architecture, world-building, dialogue coaching, editing/review, outlining, content strategy, believability auditing, and prose style/voice analysis. Includes genre-specific guides, templates, and quality checklists.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.