chorus-cli

Installs and configures the chorus CLI to manage agents and call Chorus MCP tools from the shell.

1.2k|104|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/Chorus-AIDLC/Chorus --skill chorus-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chorus-cli
Source: https://github.com/Chorus-AIDLC/Chorus/tree/main/plugins/chorus/skills/chorus-cli
Command: npx skills add https://github.com/Chorus-AIDLC/Chorus --skill chorus-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @chorus-aidlc/chorus.

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.

Frequently Asked Questions about chorus-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install the chorus CLI?

Install the chorus CLI globally with npm using `npm install -g @chorus-aidlc/chorus`. Verify the installation with `chorus --version`, which must be 0.17.0 or higher to provide the `chorus agents` and `chorus mcp` subcommands.

How do I configure multiple coding agents with chorus?

Run `chorus agents add` to detect installed coding agents, install each one's Chorus plugin, and seed credentials in ~/.chorus/daemon.json. The command is idempotent and safe to re-run, with flags like --all, --agents, and --api-key for control.

How do I call a Chorus MCP tool from the command line?

Use `chorus mcp call <tool> '<json>'` to invoke any Chorus MCP tool from the shell. For large content, pass `--arg-file content=<file>` to stream a file's raw bytes into the JSON argument without re-typing through the model.

What environment variables does the chorus CLI need?

The chorus CLI uses CHORUS_URL for the instance URL, CHORUS_API_KEY for an agent API key, and optionally CHORUS_AGENT_PROFILE to select a configured agent. When CHORUS_AGENT_PROFILE is set, the key resolves from ~/.chorus/daemon.json so CHORUS_API_KEY is not required.

Why does chorus mcp fail with an older CLI version?

The `chorus mcp` subcommand requires chorus version 0.17.0 or higher. Older versions lack this subcommand entirely, so upgrade by reinstalling the latest @chorus-aidlc/chorus package globally with npm.