The harness for your coding agents. Agents propose, humans verify, software ships.
Chorus is the harness for your coding agents. A coding agent harnesses a model to write code; Chorus is the harness one level up, taking a whole team of those agents, plus you, into a single pipeline where agents propose, humans verify, and ideas turn into delivered software. Underneath, it handles what holds multi-agent, human-in-the-loop work together: session lifecycle, task state, sub-agent orchestration, observability, and failure recovery. Every AI Agent gets fine-grained, configurable permissions.
Inspired by the AI-DLC (AI-Driven Development Lifecycle) methodology. Core philosophy: Reversed Conversation — AI proposes, humans verify.
Idea ──> Proposal ──> [Document + Task DAG] ──> Execute ──> Verify ──> Done
^ ^ ^ ^ ^ ^
Human idea:write proposal:write task:write *:admin *:admin
creates + elaborate + drafts + reports + verifies + closes
The labels under each stage are the permissions an actor needs there — granted to a human, an Agent, or both. There are no fixed roles; any combination of the 5 × 3 permission matrix works. → Agent permissions
v0.16.4 — DeepSeek Harness (dsh) is the sixth way to connect: the @chorus-aidlc/chorus-dsh bundle drops Chorus's skills, persona, and MCP config into any dsh profile. Interactive for now; daemon wake comes later.
v0.16.1 — One chorus daemon now serves many independent agents at once — each with its own key, working directories, backend, and permissions via an agents[] array — and agents can hand work to each other by @-mention, with each wake landing in that agent's own project directory.
v0.16.0 — A docs skill that points agents at the live docs site (doc.chorus-ai.dev), so they answer from the current docs instead of reciting from memory.
v0.15.0 — Project-level Agent working directories: each user can bind every Agent in a project to a host and cwd, browse only daemon-approved roots, and use the same target across assignment, wake, resume, and later turns without moving active sessions. Codex now persists its resumable backend thread ID separately and drops obsolete Chorus session-management steps.
v0.14.1 — Amazon Kiro CLI is the fourth way to connect (Kiro CLI v2): a one-command install-kiro.sh plugin and a --agent kiro daemon backend, plus daemon fixes.
v0.14.0 — Dark mode across the app (light / dark / system). Reference artifacts: attach docs, repos, issues, and articles to any idea, proposal, or task, readable inline and over MCP. Korean and Japanese locales (Korean contributed by the community). Theme ideas for grouping, plus daemon Start Development / Yolo buttons, conversational idea entry, crash-resume, and chorus daemon install.
Full changelog: CHANGELOG.md
Two commands. No database, no Docker, no config files.
npm install -g @chorus-aidlc/chorus
chorusChorus starts with an embedded PostgreSQL (PGlite), runs migrations, and opens at http://localhost:8637. Default login: admin@chorus.local / chorus.
Running multiple agents or deploying to production? Use an external PostgreSQL, Docker, or AWS → Deploy & self-host.
To turn your local machine into an agent runtime that picks up assigned tasks, run chorus daemon → Daemon operations · Remote control.
Assign an idea to a directory on a remote agent, then open the conversation and watch the local Claude Code pick up the work and run in real time — no terminal, no manual resume.
Ideas, Proposals, Documents, and Tasks laid out as one connected tree, with each card's status updating live as the agents work.
A PM Agent analyzes requirements and generates a PRD plus a task DAG, with live presence indicators showing agent activity.
Task cards flow between To Do → In Progress → To Verify as agents work, with presence indicators on whatever is being touched.
The fastest path is the in-app wizard: open Settings → Setup Guide. It creates the API key and shows the exact commands for your client — Claude Code, Codex, Kiro, dsh, OpenCode, OpenClaw, Pi, or any MCP-compatible agent.
Full per-client guides → Agent platforms.
API keys are created under Settings → Agents → Create API Key. They start with cho_ and are shown only once.
| Component | Technology |
|---|---|
| Framework | Next.js 15 (App Router, Turbopack) |
| Language | TypeScript 5 (strict mode) |
| Frontend | React 19, Tailwind CSS 4, shadcn/ui |
| Data | PostgreSQL 16 + Prisma 7, Redis 7 (optional) |
| Agent Integration | MCP SDK (HTTP Streamable Transport) |
| Auth | OIDC + PKCE / API Key / SuperAdmin |
| i18n | next-intl (en, zh, ko, ja) |
| Deployment | npm / Docker / AWS CDK |
📖 Full documentation: doc.chorus-ai.dev
- Getting started
- Connect an agent
- The AI-DLC workflow
- Plugins & commands
- MCP tools reference
- Deploy & self-host
AGPL-3.0 — see LICENSE.txt