by Chorus-AIDLC
The Agent Harness for AI-Human Collaboration, inspired by the AI-DLC (AI-Driven Development Lifecycle)
# Add to your Claude Code skills
git clone https://github.com/Chorus-AIDLC/ChorusChorus is an agent harness — the infrastructure that wraps around LLM agents to manage session lifecycle, task state, sub-agent orchestration, observability, and failure recovery. It lets multiple AI Agents (PM, Developer, Admin) and humans collaborate through the full workflow from requirements to delivery.
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 PM Agent PM Agent Dev Agent Admin Admin
creates analyzes drafts PRD codes & reviews closes
& plans & tasks reports & verifies
v0.6.2 — Embedded PGlite mode (zero-dependency deployment), structured logging with Pino, stateless MCP for horizontal scaling, default port changed to 8637.
v0.6.1 — /yolo skill: full-auto AI-DLC pipeline (Idea → Proposal → Execute → Verify) with Agent Team parallel execution.
v0.6.0 — IdeaTracker dashboard, independent review agents (proposal-reviewer + task-reviewer), real-time agent presence indicators, cross-column Kanban animation.
v0.5.1 — New user onboarding wizard, UI animation system, quick-dev skill (skip-proposal workflow).
v0.5.0 — Universal search (Cmd+K across 6 entity types), rich claim/assign response.
No comments yet. Be the first to share your thoughts!
Full changelog: CHANGELOG.md
Run Chorus locally with two commands — no database, no Docker, no config files needed.
npm install -g @chorus-aidlc/chorus
chorus
That's it. Chorus starts with an embedded PostgreSQL (PGlite), runs migrations automatically, and opens at http://localhost:8637.
Note: PGlite is an embedded, single-process PostgreSQL — great for local single-user usage, but its connection handling has limits under concurrent load. If you plan to run multiple agents or users simultaneously, use an external PostgreSQL via
DATABASE_URL=postgresql://...or the full Docker Compose stack.
Default login: admin@chorus.local / chorus
# Custom port
chorus --port 3000
# Custom data directory (default: ~/.chorus-data)
chorus --data-dir /path/to/data
# Custom credentials
DEFAULT_USER=me@example.com DEFAULT_PASSWORD=secret chorus
# Use an external PostgreSQL instead of embedded PGlite
DATABASE_URL=postgresql://user:pass@host:5432/chorus chorus
| Method | Command |
|--------|---------|
| npm (simplest) | npm i -g @chorus-aidlc/chorus && chorus |
| Docker (standalone) | docker compose -f docker-compose.local.yml up |
| Docker (full stack) | docker compose up (PostgreSQL + Redis + Chorus) |
| AWS CDK | Deploy to AWS |

Watch a PM Agent analyze requirements and generate a proposal with PRD and task DAG — with real-time presence indicators showing agent activity.

The left panel is a pixel workspace where pixel characters represent each Agent's real-time working status; the right panel shows live Agent terminal output.

The Kanban board updates automatically as Agents work, with task cards flowing between To Do → In Progress → To Verify in real time. Agent presence indicators highlight which resources are being worked on.

Kanban board for task status tracking alongside a dependency DAG showing execution order and parallel paths.

PM Agents clarify requirements through structured Q&A rounds before creating Proposals. The panel shows idea details alongside completed elaboration rounds with answers and category tags.

Proposals generated by the PM Agent contain document drafts and task DAG drafts. Admins review and approve or reject on this panel.

Dev Agent self-checks and Admin reviews each acceptance criterion independently, with structured pass/fail evidence for every item.

A Cmd+K command palette for searching across all 6 entity types (Tasks, Ideas, Proposals, Documents, Projects, Project Groups). Supports scope filtering (Global / Group / Project), filter tabs per entity type, and keyboard navigation. Both the Web UI and AI agents (via chorus_search MCP tool) share the same search backend.
┌──────────────────────────────────────────────────────────────────┐
│ Chorus — Agent Harness (:8637) │
│ │
│ ┌── Harness Capabilities ───────────────────────────────────┐ │
│ │ Session Lifecycle │ Task State Machine │ Context Inject │ │
│ │ Sub-Agent Orchestration │ Observability │ Failure Recovery│ │
│ └───────────────────────────────────────────────────────────┘ │
│ │
│ ┌── Chorus Plugin (lifecycle hooks) ────────────────────────┐ │
│ │ SubagentStart/Stop │ Heartbeat │ Skill & Context Inject │ │
│ └───────────────────────────────────────────────────────────┘ │
│ │
│ ┌── API Layer ──────────────────────────────────────────────┐ │
│ │ /api/mcp — MCP HTTP Streamable (50+ tools, role-based) │ │
│ │ /api/* — REST API (Web UI + SSE push) │ │
│ └───────────────────────────────────────────────────────────┘ │
│ │
│ ┌── Service Layer ──────────────────────────────────────────┐ │
│ │ AI-DLC Workflow │ UUID-first │ Multi-tenant │ │
│ └───────────────────────────────────────────────────────────┘ │
│ │
│ ┌── Web UI (React 19 + Tailwind + shadcn/ui) ──────────────┐ │
│ │ Kanban │ Task DAG │ Proposals │ Activity │ Sessions │ │
│ └───────────────────────────────────────────────────────────┘ │
└──────────────────────────────────────────────────────────────────┘
↑ ↑ ↑ ↑
PM Agent Developer Agent Admin Agent Human
(LLM) (LLM) (LLM) (Browser)
│
┌──────────▼──────────┐ ┌─────────────────────┐
│ PostgreSQL + Prisma │ │ Redis (optional) │
└─────────────────────┘ │ Pub/Sub for SSE │
└─────────────────────┘
| Package | Description |
|---------|-------------|
| packages/openclaw-plugin | OpenClaw Plugin — Connects OpenClaw to Chorus via persistent SSE + MCP bridge. |
| packages/chorus-cdk | AWS CDK — Infrastructure-as-code for deploying Chorus to AWS. |
| Component | Technology | |-----------|-----------| | Framework | Next.js 15 (App Router, Turbopack) | | Language | TypeScript 5 (strict mode) | | Frontend | React 19, Tailwind CSS 4, shadcn/ui (Radix