chorus-codes 0.7.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for describing the origin of the Work and
+      reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Support. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or support.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 99x Agency
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied. See the License for the specific language governing permissions
+   and limitations under the License.

package/README.md

@@ -0,0 +1,423 @@
+<div align="center">
+
+<img src="docs/images/logo.png" alt="Chorus" width="120" />
+
+# Chorus
+
+**A second opinion (and a third) before you ship AI-written code — using the AI subscriptions you already pay for.**
+
+2–3 *different* AI tools review the same change in parallel, only green-lighting when they agree. Runs on your existing Claude Pro / ChatGPT Plus / Gemini Advanced — typical review costs **$0** out of pocket.
+
+[![CI](https://github.com/chorus-codes/chorus/actions/workflows/ci.yml/badge.svg)](https://github.com/chorus-codes/chorus/actions/workflows/ci.yml)
+[![npm](https://img.shields.io/npm/v/chorus-codes?color=22c55e)](https://www.npmjs.com/package/chorus-codes)
+[![License](https://img.shields.io/badge/license-Apache%202.0-blue)](./LICENSE)
+[![Status](https://img.shields.io/badge/status-v0.7-brightgreen)]()
+[![Node](https://img.shields.io/badge/node-%E2%89%A520-339933)]()
+
+[Website](https://chorus.codes) · [Roadmap](./ROADMAP.md) · [Issues](https://github.com/chorus-codes/chorus/issues)
+
+</div>
+
+---
+
+<div align="center">
+
+<img src="docs/images/hero-demo.gif" alt="Six AI reviewers streaming verdicts in parallel — Chorus running live" width="800" />
+
+**One AI writes. Three review. You ship only when they agree — using AI subscriptions you already pay for.**
+
+</div>
+
+---
+
+## The problem Chorus solves
+
+🤖 **AI coding tools are confident — and wrong about 5% of the time** in subtle ways that are hard to spot until production.
+
+🪞 **The model that wrote your code can't see its own blind spots.**
+Asking GPT to review GPT's work is theatre — same training, same biases.
+
+💸 **Multi-AI review on raw API keys gets expensive fast.**
+Every diff × 3 reviewers × pay-per-token = real money. So nobody does it routinely.
+
+### Chorus fixes all three
+
+✅ **Different vendors review each other.**
+Claude writes, GPT and Gemini check it. Different blind spots cover each other. Disagreement = red flag *before* you merge.
+
+✅ **Uses your existing AI subscriptions.**
+You're already paying for Claude Pro / ChatGPT Plus / Gemini Advanced (~$20/mo each). Chorus drives them headlessly through their CLIs — every multi-AI review costs **$0 out of pocket**, just counts against the quota you already have. Per-token API users save 10-100× vs running the same prompts directly.
+
+✅ **Local-first, zero markup.**
+Your code never reaches a new vendor. Chorus runs on your laptop, talks to the AI tools you already trust, and shuts up. Open source, Apache-2.0.
+
+That's the whole pitch.
+
+---
+
+## Real moments where this matters
+
+🚨 **You asked Claude to write a `divide(a, b)` helper.**
+It says "looks correct!" You ship. Production crashes at 2am because nobody handled `b = 0`.
+*With Chorus: GPT or Gemini would have flagged it in the review pass before you merged.*
+
+🔧 **You're refactoring a critical path.**
+Your AI rewrote 200 lines and says it's behaviour-equivalent. You're tired and skeptical.
+*Run it through Chorus. Three different AIs all saying "yes, equivalent" lets you sleep.*
+
+🏗️ **Big architectural call** — queue vs polling, sync vs async, this DB vs that one.
+Write a paragraph, hit Chorus. *Three different models give you three angles you hadn't thought of.*
+
+📝 **Reviewing a 600-line PR.**
+You're short on time. Paste the diff into Chorus. *Three reviewers spot the obvious bugs in 90 seconds. Your job becomes the 5% they couldn't catch.*
+
+⚔️ **Test-driven development where neither AI cheats.**
+*One AI writes tests blind to the code; another AI writes code to pass them.* Use the `red-green` template.
+
+🐛 **Hunting a flaky bug.**
+Reproduces 1-in-20, no obvious pattern. Drop the failing test + suspect code into Chorus.
+*Each reviewer attacks the bug from a different angle — race? clock skew? off-by-one? — and you land on the cause faster than walking it alone.*
+
+---
+
+## Quick start
+
+```bash
+npm i -g chorus-codes      # install
+chorus init                # finds AI tools you already have
+chorus start --ui          # opens http://localhost:5050
+```
+
+Paste a task. Hit submit. Watch the AIs argue.
+
+**Requires** Node 20+ and at least *one* of these (you probably already have one):
+
+- Claude Code, Codex CLI, Gemini CLI, OpenCode, or Kimi CLI — uses your existing subscription, no extra cost
+- *or* an OpenRouter API key (one key, 200+ models, pay-per-use)
+
+<details>
+<summary><b>Don't have any of those?</b></summary>
+
+```bash
+npm i -g @anthropic-ai/claude-code   # Anthropic — uses Claude Pro sub
+npm i -g @openai/codex                # OpenAI — uses ChatGPT Plus sub
+npm i -g @google/gemini-cli           # Google — uses Gemini Advanced sub
+```
+
+Pick whichever vendor you already pay for. Or skip CLIs entirely and add an OpenRouter key in Settings after `chorus init`.
+
+</details>
+
+---
+
+## What it looks like
+
+<table>
+<tr>
+<td width="50%" align="center">
+<b>Live review</b><br/>
+<img src="docs/images/run-page.png" alt="Three reviewers streaming verdicts in real-time" width="100%" /><br/>
+<sub>Each AI streams its thinking live as it reviews.</sub>
+</td>
+<td width="50%" align="center">
+<b>Verdict</b><br/>
+<img src="docs/images/verdict.png" alt="Final converged verdict with merged diff" width="100%" /><br/>
+<sub>Agreement = green. Disagreement = retry with their feedback.</sub>
+</td>
+</tr>
+<tr>
+<td width="50%" align="center">
+<b>Templates</b><br/>
+<img src="docs/images/templates.png" alt="Template editor" width="100%" /><br/>
+<sub>Pre-built review patterns. Make your own in YAML.</sub>
+</td>
+<td width="50%" align="center">
+<b>From inside Claude / Cursor</b><br/>
+<img src="docs/images/mcp.png" alt="Claude Code calling Chorus" width="100%" /><br/>
+<sub>Any AI tool that speaks MCP can trigger a Chorus run.</sub>
+</td>
+</tr>
+</table>
+
+---
+
+## A real example
+
+You ask Claude to write this:
+
+```js
+function divide(a, b) {
+  return a / b;
+}
+```
+
+Submit to Chorus with the **Code Review** template (1 writer + 2 reviewers, both must agree to ship):
+
+| Step | What happens |
+|---|---|
+| 1. Claude writes | "Looks correct to me!" |
+| 2. GPT reviews in parallel | 🚨 *No type validation — `divide('a','b')` returns `NaN`* |
+| 3. Gemini reviews in parallel | 🚨 *Missing zero-check — `divide(1, 0)` returns `Infinity`* |
+| 4. Verdict | ❌ **REJECT** — both reviewers flagged real bugs |
+
+Now you know what to fix **before** you push.
+
+---
+
+## Templates: pre-built review patterns
+
+Don't figure out which AIs to use yourself. Pick a pattern that fits the moment:
+
+| Use this when... | Template |
+|---|---|
+| Pre-merge sanity check | `code-review` — 1 writer + 2 reviewers, both must agree |
+| Diagnosing a weird bug | `bug-diagnose` — one hypothesises, one challenges |
+| Big architectural call | `architect-review` — 3 different vendors critique your plan |
+| TDD where neither AI cheats | `red-green` — tests written blind to code |
+| Quick audit of a diff someone else wrote | `review-only` — paste, get 3 opinions, no writer |
+
+Make your own by dropping a YAML file in `~/.chorus/templates/`. Or duplicate one of the built-ins and tweak.
+
+<details>
+<summary><b>Custom template example</b></summary>
+
+```yaml
+id: security-pre-merge
+label: Security Pre-Merge
+description: Sentinel persona on every reviewer; everyone must approve.
+slots:
+  doer:
+    lineage: anthropic
+    model: claude-sonnet-4-6
+  reviewers:
+    - { lineage: openai,   model: codex,                 persona: sentinel }
+    - { lineage: google,   model: gemini-2.5-pro,        persona: sentinel }
+    - { lineage: opencode, model: opencode-go/kimi-k2.6, persona: sentinel }
+quorum:
+  type: unanimous
+```
+
+</details>
+
+---
+
+## Reviewer personas
+
+Each reviewer can wear a "hat" — a focus area Chorus prepends to their prompt:
+
+| Persona | What they look for |
+|---|---|
+| 🛡️ **Sentinel** | Security holes, auth bypass, injection |
+| 🗺️ **Cartographer** | Cross-platform issues (Windows vs Mac, browser support) |
+| 💰 **Accountant** | Cost regressions (extra DB queries, API calls) |
+| ⚡ **Profiler** | Performance regressions |
+| 🔍 **Inspector**, 📦 **Quartermaster**, 🛎️ **Concierge**, 🏛️ **Conservator**, 📚 **Librarian**, 🌐 **Translator** | …and more — see Personas page in cockpit |
+
+Different personas reviewing the same change = wider net.
+
+---
+
+## Why "different vendors" matters
+
+You can run Chorus with three Claudes. We let you. But the value drops a lot.
+
+A second Claude reviewing the first Claude's work is theatre — same training, same blind spots. Mix vendors (Claude + GPT + Gemini) and you get genuinely different angles, because they were trained on different data with different biases.
+
+Templates let you encode this: each reviewer slot has a `lineage` (anthropic / openai / google / opencode / moonshot). Built-in templates mix vendors automatically.
+
+---
+
+## What does it cost?
+
+Two paths, depending on how you already pay for AI:
+
+**Using subscriptions** (Claude Pro / ChatGPT Plus / Gemini Advanced — ~$20/mo each)
+A typical review = **$0** out of pocket. Counts against the quota you already have.
+
+**Using API keys** (pay-per-use)
+A typical code-review run = **$0.30 to $1.50**, depending on diff size. If reviewers disagree and retry, 2–3× worst case.
+
+Chorus adds **zero markup**. We don't see your tokens.
+
+---
+
+## Permissions & safety
+
+Reviewers run on your machine. You decide how much trust to give them:
+
+| Mode | Read code | Write code | Network | When to use |
+|---|:---:|:---:|:---:|---|
+| 🔒 **Strict** | ✅ | ❌ | ❌ | Reviewing a diff you don't trust |
+| 📁 **Workspace** *(default)* | ✅ | ✅ inside chat dir | ❌ | Day-to-day |
+| 🔓 **Full** | ✅ | ✅ anywhere | ✅ | Personal machine, full trust |
+
+Configure on first run, or anytime at *Settings → Permissions*.
+
+> **Trust model in plain English.** "Workspace" means the reviewer can write files inside its working directory and run scoped commands, but can't reach the internet or write outside the sandbox. "Full" means anything-goes — only enable on a personal machine you own. Run `chorus doctor` to verify each AI tool got the sandbox you set.
+
+---
+
+## Use it from inside another AI tool
+
+Chorus speaks MCP — the protocol Claude Code, Cursor, Codex, Gemini CLI etc. use to talk to other tools. So you can trigger a Chorus run *from inside* the AI tool you're already using.
+
+Example, inside Claude Code:
+
+> *"Run code-review on the diff against main using Chorus"*
+
+Claude Code calls Chorus → Chorus fans out to other AI tools → results stream back into Claude Code. Useful when you want a second opinion without leaving the editor.
+
+`chorus init` wires up MCP for the orchestrators it detects (Claude / Codex / Gemini / Cursor / Windsurf, etc.).
+
+---
+
+## Compared to other code-review tools
+
+| | **Chorus** | CodeRabbit | Greptile | Cursor Review | GitHub Copilot |
+|---|:---:|:---:|:---:|:---:|:---:|
+| Multiple AI vendors review the same change | ✅ | ❌ | ❌ | ❌ | ❌ |
+| Uses your existing AI subscriptions | ✅ | ❌ | ❌ | ❌ | ❌ |
+| Runs locally (your code never leaves your existing AI vendors) | ✅ | ❌ | ❌ | partial | ❌ |
+| Open source (modify + self-host) | ✅ Apache-2.0 | ❌ | ❌ | ❌ | ❌ |
+| Custom review patterns | ✅ | partial | ❌ | ❌ | ❌ |
+
+**The unique thing:** your code never goes to a new vendor. Chorus just orchestrates the AI tools you already use.
+
+---
+
+## Commands
+
+```bash
+chorus init             # one-time: detect + connect AI tools
+chorus start --ui       # boot + open browser
+chorus stop             # shut it down
+chorus status           # is it running?
+chorus doctor           # diagnose AI tool detection / sandbox issues
+```
+
+---
+
+## Telemetry
+
+Chorus pings home once on startup and once every 24h. The payload is fixed:
+
+```json
+{
+  "schema": 1,
+  "installId": "<random uuid>",
+  "version": "0.7.0",
+  "os": "linux", "arch": "x64", "node": "22",
+  "daemonUptimeSeconds": 86400,
+  "chatsLast24h": 12
+}
+```
+
+**Never sent:** chat content, prompts, file paths, repo paths, model names, voice/template names, hostnames, IPs, API keys.
+
+Turn it off any of three ways:
+
+```bash
+export CHORUS_TELEMETRY=0           # env var
+touch ~/.chorus/no-telemetry        # touch-file
+# or click "Off" in cockpit Settings → Telemetry
+```
+
+The install ID lives at `~/.chorus/install-id` — `rm` it for a fresh one.
+
+---
+
+## Roadmap
+
+- [x] **v0.5** — Daemon + cockpit + 4 AI vendors
+- [x] **v0.6** — MCP server, persona system
+- [x] **v0.7** — OpenRouter integration, voices table, real-time sidebar
+- [ ] **v0.8** — Multi-stage review (write → review → fix → re-review)
+- [ ] **v0.9** — Per-voice persona overrides
+- [ ] **v1.0** — Hosted GitHub App + cloud fan-out
+
+Full picture in [ROADMAP.md](./ROADMAP.md).
+
+---
+
+<details>
+<summary><b>How it works (under the hood)</b></summary>
+
+```mermaid
+flowchart TB
+    User([👤 You])
+    Cockpit[Cockpit<br/>:5050 · web UI]
+    Daemon[Chorus daemon<br/>:7707 · local server]
+    DB[(SQLite<br/>~/.chorus/chorus.db)]
+    MCP[MCP server<br/>for editor integrations]
+
+    Claude[🤖 Claude<br/>writer]
+    Codex[🦾 GPT<br/>reviewer]
+    Gemini[💎 Gemini<br/>reviewer]
+
+    User -->|paste task| Cockpit
+    Cockpit <-->|REST + live updates| Daemon
+    Daemon <--> DB
+    Daemon -->|spawn| Claude
+    Daemon -->|spawn| Codex
+    Daemon -->|spawn| Gemini
+    User -.->|"call Chorus from your AI"| MCP --> Daemon
+
+    classDef user fill:#fef3c7,stroke:#f59e0b,color:#000
+    classDef chorus fill:#dbeafe,stroke:#3b82f6,color:#000
+    classDef llm fill:#fce7f3,stroke:#ec4899,color:#000
+    class User user
+    class Daemon,Cockpit,MCP,DB chorus
+    class Claude,Codex,Gemini llm
+```
+
+**Three pieces:**
+
+- **Daemon** — small local server (port 7707) that spawns AI tools as subprocesses, parses their output, and tracks state in a SQLite database at `~/.chorus/chorus.db`.
+- **Cockpit** — the web UI at port 5050 (Next.js). Templates, chats, voices, settings.
+- **MCP server** — lets *other* AI tools (Claude Code, Cursor, etc.) call Chorus programmatically.
+
+Each AI runs as an isolated subprocess. Chorus reads their structured output (stream-JSON), compares against the template's quorum rule, and emits a verdict. Nothing leaves your machine except the calls to the AI vendors you already use.
+
+Code layout:
+- `src/daemon/` — Fastify server + agent shims (one per AI tool)
+- `src/app/` — Next.js cockpit
+- `src/mcp/` — JSON-RPC MCP server
+- `src/lib/db/` — schema + migrations
+
+</details>
+
+---
+
+## Contributing
+
+PRs welcome.
+
+```bash
+git clone https://github.com/chorus-codes/chorus.git
+cd chorus && pnpm install
+pnpm dev:daemon   # daemon on :7707
+pnpm dev          # cockpit on :5050
+pnpm test         # full suite
+```
+
+Read [`AGENTS.md`](./AGENTS.md) first — Next.js 16 has breaking changes from older versions. Coverage target on new code: 80%+.
+
+We dogfood: PRs to Chorus go through Chorus before merging.
+
+See [CONTRIBUTING.md](./CONTRIBUTING.md) for the full guide.
+
+---
+
+## Links
+
+- 🌐 Website: <https://chorus.codes>
+- 🗺️ Roadmap: [./ROADMAP.md](./ROADMAP.md)
+- 🐛 Issues: <https://github.com/chorus-codes/chorus/issues>
+- 💬 Discussions: <https://github.com/chorus-codes/chorus/discussions>
+- 🐦 Twitter / X: [@chorus_codes](https://twitter.com/chorus_codes)
+
+---
+
+## License
+
+[Apache-2.0](./LICENSE). Use it however you want, including commercially.

package/assets/slash-commands/chorus.md

@@ -0,0 +1,35 @@
+---
+description: Run a multi-LLM Chorus peer review on a task
+argument-hint: [template] <work description>
+---
+
+Route this request to the Chorus MCP server. Use the `mcp__chorus__*` tools — do NOT try to do the review yourself.
+
+**Arguments:** $ARGUMENTS
+
+## Steps
+
+1. **Resolve the template.** If $ARGUMENTS starts with a known template id (e.g. `bug-diagnose`, `code-review`, `red-green`, `architecture`), peel it off as the template and treat the rest as the work payload. Otherwise call `mcp__chorus__list_templates`, show the user `name + description` for each, and ask which to use. Don't guess — picking the wrong template wastes a multi-minute, multi-LLM run.
+
+2. **Create the chat.** Call `mcp__chorus__create_chat` with `{ template, work }`. Capture the returned `chatId`.
+
+3. **Wait for the result.** Call `mcp__chorus__wait_for_chat({ chatId })`. Stream any progress notifications back to the user as they arrive (template phases, reviewer verdicts).
+
+4. **Summarise.** When the chat completes, report:
+   - The final verdict (approved / changes-requested / blocked)
+   - The 3-5 highest-priority findings, each with a one-line rationale and a file:line pointer if the reviewer gave one
+   - The Chorus cockpit URL for the run if available (typically `http://127.0.0.1:5050/runs/<chatId>`)
+
+   Do not paste the full transcript. The user can open the run page for that.
+
+## Failure handling
+
+- If `create_chat` returns `MCP server chorus not connected` or any tool throws a connection error, tell the user to run `chorus start` (or `chorus status` to check) and retry. Do not fall back to doing the review yourself.
+- If the chat is `blocked` (waiting for human input), surface the question verbatim and stop — let the user respond via `mcp__chorus__resume_chat`.
+- If the chat fails (`failed` status), report the error from `get_chat_status` and suggest the cockpit URL for the full log.
+
+## Hard rules
+
+- Never substitute your own review for a Chorus run when the user asked for `/chorus` — the whole point is cross-lineage second opinions.
+- Never invent a template id. If $ARGUMENTS doesn't match a real template, ask.
+- Never call `cancel_chat` unless the user explicitly asks to abort.