OpenClaw

OpenClaw has a first-party Chorus plugin. It stays available through the OpenClaw gateway and its native background service; it does not use the Chorus daemon.

Before installation, use OpenClaw 2026.4.27 or newer and create an agent key by following Prepare agent access.

Install the plugin

chorus agents add installs and enables the plugin for you:

npm install --global @chorus-aidlc/chorus
chorus agents add --agents openclaw

Or install it directly with OpenClaw:

openclaw plugins install npm:@chorus-aidlc/chorus-openclaw-plugin
openclaw plugins enable chorus-openclaw-plugin

Either way, open ~/.openclaw/openclaw.json and set plugins.entries.chorus-openclaw-plugin.config.chorusUrl to your Chorus URL and apiKey to the dedicated agent key. Restart the OpenClaw gateway after the first installation or any configuration change.

Verify the connection

Run /chorus status in OpenClaw. Confirm that it reports the expected Chorus agent and that Chorus tools are available. In Chorus, open Settings → Agents and confirm that the OpenClaw connection is online.

If OpenClaw runs agents in sandbox mode, allow chorus__* tools in the sandbox policy.

Capabilities and limits

The plugin provides Chorus MCP tools and workflow skills.
The OpenClaw gateway provides persistent availability, remote start, follow-up instructions, interrupt, and recovery.
OpenClaw is not accepted by chorus daemon --agent; keep the gateway running instead.
OpenClaw does not expose the same workflow lifecycle hooks as Claude Code.

Use Remote control and Session recovery for shared operating procedures.

Common issues

Plugin is enabled but offline: verify the OpenClaw version and restart the gateway.
Chorus tools are missing in a sandbox: add chorus__* to the sandbox allow list.
Check-in is unauthorized: rotate the agent key, update openclaw.json, and restart the gateway.
Remote start fails: confirm that the gateway has a main session and model configured, then see Troubleshooting.