What problem does it solve?
Setting up Chorus across multiple coding agents and calling Chorus MCP tools from the shell requires knowing the right commands, environment variables, and identity resolution rules, which are easy to get wrong without a single reference.
Core Features & Use Cases
- CLI Installation & Versioning: Install
@chorus-aidlc/chorus globally via npm and verify the version meets the >= 0.17.0 requirement for chorus agents and chorus mcp.
- Agent Management: Use
chorus agents to list, add, and remove configured agents in ~/.chorus/daemon.json, including plugin installation and credential seeding for detected coding agents.
- MCP Operations from the Shell: Call any Chorus MCP tool with
chorus mcp call, stream file bytes into arguments via --arg-file, check identity with whoami, and list permitted tools.
- Use Case: A developer onboards a new machine, runs
chorus agents add to configure all installed coding agents at once, then uses chorus mcp call with --arg-file to submit a large design document without re-typing it through the model.
Quick Start
Install the chorus CLI globally with npm, then run chorus agents add to configure your coding agents and chorus mcp whoami to verify your identity.