Symphony++ is a local planning and delivery cockpit for coding agents. Its ledger, MCP tools, and dashboard connect WorkRequests, bounded WorkPackages, decisions, blockers, and GitHub delivery evidence.
A human and agent can explore a problem before creating a WorkRequest. An architect then slices and oversees tracked delivery. Ordinary workers and coordinators also work without a backend; optional Solo Sessions provide lightweight planning memory through MCP. Symphony++ does not own model accounts or terminal sessions.
Ordinary workers receive an assignment, implement it, run required native checks and review, and return a PR or evidence. The architect coordinates ownership, dependencies, explicit blockers, readiness, and delivery; worker MCP calls and duplicate status/review reporting are optional.
Windows installation and connection for Codex or Claude Code:
Follow Install and run for the Skills route and the marketplace alternative. Main is the normal branch; beta is an isolated preview. Both follow automatically published branch runtimes. Close clients, update, run setup and open fresh sessions to adopt the latest published build.
Portable procedures without runtime installation:
npx skills add https://github.com/JJLiebig/symphony-plus-plus/tree/mainThis installs procedures only. See Portable skills for host selection, updates, removal, and separate MCP setup.
For skill-only Codex use, choose a separate beta home and add the marketplace:
$env:CODEX_HOME = Join-Path $env:USERPROFILE '.codex-sympp-beta'
New-Item -ItemType Directory -Force -Path $env:CODEX_HOME | Out-Null
codex plugin marketplace add https://github.com/JJLiebig/symphony-plus-plus --ref beta
codex plugin marketplace upgrade symphony-plus-plusChoose the skill-only plugin for ordinary workers/coordinators:
codex plugin add symphony-plus-plus@symphony-plus-plusUpdate packages and open a fresh Codex session:
codex plugin marketplace upgrade symphony-plus-plusDo not install both plugins in the same Codex home unless you intentionally want both skill prefixes visible. The MCP companion starts or reuses the local runtime and serves its dashboard. See Runtime for actual endpoint lookup, lifecycle, beta isolation, and repair.
- Documentation index: current system, operations, security, development, and recovery.
- Default plugin and MCP companion: package boundaries.
- Product and Design: purpose and interface principles.
- Factory workflow: approved beta contract and editable human diagram.
- Upstream specification: upstream Symphony behavior.
Apache 2.0. See LICENSE.