commanderclaw-openclaw-plugin
v1.1.2
Published
Connect to CommanderClaw coordination server as a node for multi-agent task coordination
Downloads
402
Maintainers
Readme
@openclaw/commanderclaw
OpenClaw channel plugin for CommanderClaw multi-agent coordination.
Quick Start
1. Start CommanderClaw
commanderclaw gateway startThis starts:
- Server on port 19739
- Web Console on port 19730
2. Install Plugin
cd plugins/commanderclaw
npm run build
openclaw plugins install .3. Configure
Add to ~/.openclaw/openclaw.json:
{
"channels": {
"commanderclaw": {
"enabled": true,
"serverUrl": "ws://127.0.0.1:19739/ws",
"token": "your-secret-token",
"deviceName": "OpenClaw Agent"
}
}
}4. Restart OpenClaw
openclaw gateway restartConfiguration
| Option | Type | Required | Default | Description |
|--------|------|----------|---------|-------------|
| enabled | boolean | No | true | Enable/disable the channel |
| serverUrl | string | Yes | - | WebSocket URL (ws://127.0.0.1:19739/ws) |
| token | string | No | - | Authentication token |
| deviceName | string | No | "OpenClaw Agent" | Node name |
| autoConnect | boolean | No | true | Auto-connect on start |
Features
Chat Integration
Once connected, OpenClaw can receive and respond to messages from the CommanderClaw Web Console:
- Open http://127.0.0.1:19730
- Click "Set as Commander" to become the King node
- Send messages to the OpenClaw node
- OpenClaw processes with its configured AI model and responds
Tools
- commanderclaw_nodes - List cluster nodes
- commanderclaw_task - Manage tasks (create, list, get, abort, pause, resume)
- commanderclaw_status - Check connection status
- commanderclaw_command - Send King commands
Architecture
This is a channel plugin (not a regular plugin), which means:
- Configuration goes under
channels.commanderclaw - Bidirectional messaging support
- Integrates with OpenClaw's reply dispatch system
Development
# Install dependencies
npm install
# Build
npm run build
# Install to OpenClaw
openclaw plugins install .Troubleshooting
Connection refused
# Check if server is running
commanderclaw gateway status
# Start if not running
commanderclaw gateway startPlugin not loading
# Check installation
ls ~/.openclaw/extensions/commanderclaw/
# Reinstall
npm run build && openclaw plugins install .Messages not received
Ensure the web console node is set as Commander (King node can send messages to soldiers).
Logs
# Server logs
tail -f /tmp/commanderclaw-server.log
# OpenClaw logs
tail -f /tmp/openclaw/openclaw-$(date +%Y-%m-%d).log | grep -i commanderclawLicense
MIT
