OpenClaw channel plugin — bridges your local OpenClaw agent to Octer.ai via WebSocket, enabling remote tool execution from the Octer.ai cloud.
# 1. Install plugin
openclaw plugins install octer-channel
# 2. Set your API Key
openclaw config set plugins.entries.octer-channel.config.apiKey "evo_YOUR_KEY"
# 3. Restart gateway
openclaw gateway restart- Visit octer.ai/workspace
- Click Me → Settings → API Keys → Create Key
- Copy the key (starts with
evo_)
For development or offline installation:
openclaw plugins install /path/to/octer-channel# Check plugin is loaded
openclaw plugins info octer-channel
# Check channel is configured and enabled
openclaw channels list
# Check channel is running (requires gateway)
openclaw channels statusExpected output:
- Octer default (Octer): enabled, configured, running
All configuration is stored in ~/.openclaw/openclaw.json under plugins.entries.octer-channel.config:
{
"plugins": {
"entries": {
"octer-channel": {
"enabled": true,
"config": {
"apiKey": "evo_your_key_here"
}
}
}
}
}Set config via CLI:
# Set API Key
openclaw config set plugins.entries.octer-channel.config.apiKey "evo_YOUR_KEY"
# Enable / disable
openclaw plugins enable octer-channel
openclaw plugins disable octer-channelRun independently without the OpenClaw gateway:
echo "API_KEY=evo_your_key_here" > .env
npm startOcter.ai Cloud ←──WebSocket──→ octer-channel plugin ←──CLI──→ OpenClaw Agent
(tool_request) (openclaw agent -m)
(tool_response)
The plugin receives tool_request messages from Octer.ai, dispatches each request to a local openclaw agent process, and sends the result back as tool_response.
| Problem | Solution |
|---|---|
| Channel shows "not configured" | Set API Key: openclaw config set plugins.entries.octer-channel.config.apiKey "evo_..." |
| WebSocket keeps disconnecting | Check network; the plugin auto-reconnects every 3s |
plugin not found |
openclaw plugins install octer-channel |
| Gateway not picking up changes | openclaw gateway restart or kill & re-run |