Chorus — Multi-LLM Peer Review for Code

Main

• Use it for risky diffs: paste a staged diff or PR summary and ask for reviewers to flag missing tests, race conditions, and edge cases.

• Keep costs low: README frames it as using subscriptions you already pay for, avoiding pay-per-token multi-review overhead for routine checks.

• Wire once, use everywhere: after chorus init, call it from inside your AI CLI via MCP rather than copying huge diffs manually.

• Treat reviewer disagreement as a signal: when models diverge, slow down and add targeted tests before shipping.

Source-backed notes

• README Quick start shows npm i -g chorus-codes, chorus init, and chorus start --ui for a localhost UI.
• README states chorus init registers Chorus as an MCP server across multiple AI CLIs/IDEs.
• README lists MCP tools and templates/personas for code-review style workflows.

FAQ

• Do I need API keys?: README positions it around using subscriptions you already have; some paths may use keys depending on your setup.
• How do I use it from Claude Code/Cursor?: Run chorus init once, then ask your assistant to invoke Chorus via MCP as shown in README.
• Where does it run?: Locally: README shows a UI served at http://localhost:5050 plus MCP stdio tools for clients.