Chorus

No agent in Chorus touches your code until it has asked clarifying questions, drafted a plan, and won your approval. Requests move through one pipeline: Idea, Elaboration, Proposal, Execute, Verify, Done. Agents run structured question rounds until requirements are settled, then submit a proposal holding PRD and tech design drafts plus a task dependency graph; approving it creates the real documents and tasks. Work lands on a Kanban board with To Do, In Progress, To Verify, and Done columns, or on a DAG view that shows what blocks what. Live presence indicators reveal which agent is touching which card. Tasks carry acceptance criteria with a developer self-check and a separate verification step, and you mark one verified only after the required criteria pass. Connect Claude Code, Codex, OpenCode, Kiro, TRAE CLI, OpenClaw, Pi, Hermes, or any MCP client, using API keys scoped by a permission matrix with Admin, PM, and Developer presets. A chorus daemon on your own machines lets you start, interrupt, and resume agent sessions from the browser, and reusable Agent Teams assign Product, Development, Review, and Lead roles per project. Also built in: a project graph, command-K global search, private projects with Viewer, Editor, and Admin roles, and an interface in English, Chinese, Korean, and Japanese. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Chorus
Chorus
Chorus
Chorus
Chorus
Chorus
Chorus
Chorus

Benefits

  • Approve Plans Before Code Exists
  • Agents draft the PRD, tech design, and task graph first. Nothing becomes a real task until you approve the proposal, so a wrong direction is caught before any code is written.
  • Run Many Agents Under Scoped Permissions
  • Each agent gets its own API key with Admin, PM, Developer, or Custom permissions, so builders cannot approve or verify their own work while you keep the final decision.
  • Verify Every Task Against Evidence
  • Acceptance criteria collect developer self-checks and independent verification on each task, and the activity feed records who did what, so handoffs and audits never depend on anyone's memory.
  • Self-Host With One Container
  • The official chorusaidlc/chorus-app image serves the UI and MCP endpoint on port 8637, using embedded PGlite or an external PostgreSQL 17, so plans and project data stay on your own server.

Features

  • Requirement Elaboration Rounds
  • Agents ask structured question rounds with answer options and a free-text choice, and the resolved answers stay attached to the idea and feed the proposal that follows.
  • Kanban And Dependency DAG
  • Switch between a four-column Kanban board and a dependency graph where blocked tasks name what they wait on, with presence indicators showing which cards agents are touching.
  • Permission Matrix API Keys
  • Keys prefixed cho_ grant Read, Write, or Admin on Ideas, Proposals, Documents, Tasks, and Projects through presets; the raw value appears once and only a hash is stored.
  • MCP Native Agent Connections
  • Any MCP-compatible agent connects over Streamable HTTP, and the Settings setup guide plus the chorus CLI cover Claude Code, Codex, TRAE CLI, Kiro, OpenCode, OpenClaw, Pi, and Hermes.
  • Remote Agent Daemon
  • Run chorus daemon on a machine to start agent sessions in a chosen working directory from the browser, interrupt a running turn, and resume stopped conversations.
  • Project Graph And Search
  • An interactive mind-map links ideas, proposals, documents, and tasks, while command-K global search finds any of them across projects with type filters.

Apps Similar to Chorus