Cc Orchestra

Two independently installable Claude Code plugins — orchestra (multi-agent orchestration) and orchestra-memory (cross-project graph memory) — that work standalone or together.

Quick Start (< 2 min)

claude plugin marketplace add josefkrajkar/cc-orchestra
claude plugin install orchestra@orchestra
claude plugin install orchestra-memory@orchestra   # optional but recommended
claude plugin list

Restart the session (or start a new one) so the plugins' hooks and commands load. Requirements: bash + jq for orchestra's hooks (Unix-only — macOS/Linux, no Windows), and Node.js ≥ 22.16 for orchestra-memory only (the node:sqlite builtin needs that floor for flag-free FTS5). Missing either fails open with a visible warning rather than crashing.

The two plugins

Plugin	Purpose	Docs
orchestra	Multi-agent orchestration plugin — 3-layer architecture (planning/orchestration/execution), 8 specialized agents, staged pipeline with quality gates, wisdom accumulation, file claiming, boulder session persistence. Works fully standalone.	packages/orchestra/README.md
orchestra-memory	Standalone cross-project graph-memory MCP server — SQLite-backed (node:sqlite) with FTS5 full-text search, temporal validity, and global/project/private scoping. Injects memory context at session start and after compaction. Works standalone or as orchestra's optional companion.	packages/orchestra-memory/README.md

Architecture

┌────────────────────────┐                          ┌────────────────────────┐
│       orchestra        │--ToolSearch (optional)-->│    orchestra-memory    │
│ agents/commands/skills │<--fails open if absent---│ MCP server + graph.db  │
└────────────────────────┘                          └────────────────────────┘

Each plugin resolves scripts and its own MCP server strictly under its own ${CLAUDE_PLUGIN_ROOT} — neither addresses the other's path. orchestra looks up orchestra-memory's tools via ToolSearch when present and falls back to a legacy per-project JSON file when it isn't. Full rationale: docs/architecture.md.

Install

The three supported permutations

Install	Result
Both plugins	Full experience — orchestration plus cross-project graph memory with temporal validity and scoping.
orchestra only	Orchestration works fully (agents, commands, skills, hooks). Wisdom falls back to the per-project .claude/orchestra-wisdom.json file.
orchestra-memory only	A standalone graph-memory MCP server, usable by any MCP-aware tooling, with no dependency on the orchestration plugin.

# Both
claude plugin marketplace add josefkrajkar/cc-orchestra
claude plugin install orchestra@orchestra
claude plugin install orchestra-memory@orchestra

# orchestra only
claude plugin marketplace add josefkrajkar/cc-orchestra
claude plugin install orchestra@orchestra

# orchestra-memory only
claude plugin marketplace add josefkrajkar/cc-orchestra
claude plugin install orchestra-memory@orchestra

Add --scope project to the marketplace add command to register the marketplace for a single project only, instead of for your whole user account (the default). No build step is required on the consumer's side — orchestra-memory's MCP server bundle ships prebuilt in the repo.

Soft-companion relationship

• No cross-plugin path references. orchestra ships no .mcp.json and holds no reference to orchestra-memory's mcp-server/ directory, or vice versa.
• Runtime discovery, not a hard dependency. orchestra's agents and commands look up orchestra-memory's MCP tools (memory_save, memory_search, wisdom_get, wisdom_add, etc.) via ToolSearch at runtime — they are not pre-attached.
• Independent hooks. Both plugins register their own SessionStart/PostCompact hooks; Claude Code runs both when both are installed, with no shared hook.
• Fail-open, always. Every point of contact degrades silently to "orchestra-memory absent" (not installed, uninstalled, or Node < 22.16) rather than erroring.
• Install either alone, both together, or uninstall one without the other — nothing breaks in any combination.

See docs/architecture.md for the deeper architectural rationale.

Uninstall / cleanup

# 1. Uninstall the plugin(s)
claude plugin uninstall orchestra@orchestra
claude plugin uninstall orchestra-memory@orchestra

# 2. Purge orchestra-memory's global state (only if you installed it)
rm -rf ~/.claude/orchestra-memory/graph.db ~/.claude/orchestra-memory/backups/

# 3. Purge orchestra's per-project state, run inside each project you used it in
rm -f .claude/orchestra-boulder.json .claude/orchestra-wisdom.json

~/.claude/orchestra-memory/graph.db and its backups/ directory are user-global, not per-project — deleting them removes graph memory for every project on the machine. .claude/orchestra-boulder.json and .claude/orchestra-wisdom.json are per-project; repeat step 3 for every project where you used orchestra.

Learn more

• AGENTS.md — stack, commands, conventions, and permission boundaries for coding agents working in this repo
• CONTRIBUTING.md — build/test instructions and the monorepo's cross-package contracts
• docs/architecture.md — system design, data flow, and rejected alternatives
• packages/orchestra/README.md — full feature set, agents, commands, and internals
• packages/orchestra-memory/README.md — server internals, schema, and tool reference

License

MIT — see LICENSE.