chorus-cli

# chorus-cli — using the `chorus` CLI `chorus` (published as `@chorus-aidlc/chorus`) is the one command that configures this machine's coding agents for Chorus and talks to the Chorus MCP endpoint from the shell. This is a concise reference — run `chorus --help` and `chorus <command> --help` for the full flag surface. ## 1. Install ```bash npm install -g @chorus-aidlc/chorus # unpinned — always installs the latest chorus --version # must be >= 0.17.0 (provides `chorus agents` + `chorus mcp`) ``` ## 2. Configure agents — `chorus agents` Agent configuration lives in `~/.chorus/daemon.json`; `chorus agents` is the CRUD group: - `chorus agents` (or `chorus agents list`) — list configured agents (name, UUID, backend). The API key is never printed; the agent named by `CHORUS_AGENT_PROFILE` is marked. - `chorus agents add [--agents <ids>] [--all] [--url <u>] [--api-key <cho_…>] [--yes] [--dsh-profile <name>]` — detect installed coding agents, install each one's Chorus plugin, and seed credentials (this is the former `chorus init`). Idempotent; safe to re-run. `--help` lists every flag. - `chorus agents remove <name|uuid>` — remove a configured agent from `~/.chorus/daemon.json` (matched by UUID or name; an ambiguous name → use the UUID). ## 3. Connection environment variables - `CHORUS_URL` — the Chorus instance URL. - `CHORUS_API_KEY` — an agent API key (`cho_…`). - `CHORUS_AGENT_PROFILE` — optional name or UUID of the agent to act as....