Skip to content
Chorus Chorus

Claude Code

Claude Code

Section titled “Claude Code”

Claude Code has a first-party Chorus plugin. It supports Chorus tools and workflow skills in an interactive Claude Code session, and it can run as a supported Chorus daemon backend.

Before installation, create an agent key by following Prepare agent access.

Install the plugin

Section titled “Install the plugin”

The quickest path is the chorus CLI, which installs the plugin and stores the credential for you:

Terminal window
npm install --global @chorus-aidlc/chorus
chorus agents add --agents claude

Enter the Chorus URL and agent key when prompted. chorus agents add runs claude plugin marketplace add / claude plugin install for you and writes CHORUS_URL, CHORUS_API_KEY, and CHORUS_AGENT_PROFILE into the env block of your user-global ~/.claude/settings.json, so an interactive Claude Code session authenticates with no manual environment setup. Restart Claude Code afterward.

To install by hand instead, set the credential in the launching shell:

Terminal window
export CHORUS_URL="https://chorus.example.com"
export CHORUS_API_KEY="cho_REDACTED"

Then add the plugin from inside Claude Code:

/plugin marketplace add Chorus-AIDLC/chorus
/plugin install chorus@chorus-plugins

Restart Claude Code after installation.

Enable remote start

Section titled “Enable remote start”

Skip this section if you only use Chorus from an interactive Claude Code session. Otherwise, follow Connect an agent runtime and select claude-code as the backend. Verify the connection in the foreground before using Daemon operations to keep it online.

Verify the connection

Section titled “Verify the connection”

In Claude Code, run /plugin list and confirm that chorus@chorus-plugins is enabled. Then ask Claude Code to check in to chorus. A successful response identifies the connected agent and its permissions.

For daemon mode, open Settings → Agents in Chorus and confirm that the expected host and working directory are online.

Capabilities and limits

Section titled “Capabilities and limits”
  • The plugin provides Chorus MCP tools, workflow skills, and lifecycle integration.
  • Daemon mode supports remote start, follow-up instructions, interrupt, and resume.
  • Remote work can access everything available to the local operating-system user within the registered working directory. Register only directories you trust.

Use Remote control and Session recovery for shared operating procedures.

Resume from the terminal

Section titled “Resume from the terminal”

To take over a live conversation from your own terminal, copy its session id from the chat UI (Copy session ID in the transcript header) and run, from the conversation’s working directory:

Terminal window
claude --resume <sessionId>

The copied id is the same id Chorus passes to Claude Code when it resumes a session; for a Claude Code backend it is the direct idea’s UUID. See Interrupt and resume a session for the full flow.

Common issues

Section titled “Common issues”
  • Plugin does not appear: restart Claude Code, then check /plugin list.
  • Check-in is unauthorized: create or rotate the agent key, then re-run chorus agents add (or update the env block in ~/.claude/settings.json), and restart Claude Code.
  • Daemon is offline: run chorus daemon status, then see Troubleshooting.
  • Wrong project is available: reinstall the daemon with the intended absolute --cwd value.