Usage
Options
OpenClaw Gateway WebSocket URLShort form:
-gDefault: Loaded from config.gateway.url (typically ws://127.0.0.1:18789), or GATEWAY_URL environment variableExample:What It Does
The bot command:- Connects to the OpenClaw Gateway WebSocket
- Provides an interactive terminal for:
- Checking connection status
- Sending heartbeat pings
- Viewing configuration
- Monitoring gateway events
- Handles automatic reconnection on disconnect
- Displays real-time connection status
Examples
Basic Usage
Connect to the default gateway:Custom Gateway URL
Connect to a remote gateway:Using Environment Variable
Interactive Commands
Once connected, you can use these commands:help
Display available commands:status
Check gateway connection status:ping
Send a heartbeat to the gateway:config
Show current configuration:call
Info about making calls:active
Info about viewing active calls:clear
Clear the terminal screen:quit
Exit the bot terminal:Ctrl+C or type exit or q.
Connection Status
Successful Connection
Connecting in Background
Connection Failed
Reconnection Behavior
The bot automatically reconnects if the connection is lost:- Max attempts: Configured in
config.gateway.reconnect_max_attempts(default: 5) - Base delay:
config.gateway.reconnect_base_delay(default: 1s) - Max delay:
config.gateway.reconnect_max_delay(default: 60s) - Backoff: Exponential with jitter
Integration with OpenClaw
The bot connects to the OpenClaw Gateway to:- Send call events: Transcripts, outcomes, metadata
- Receive commands: Execute ClawdBot skills
- Monitor state: Track active calls and agent status
Use Cases
Development
Monitor gateway connection during development:Debugging
Check if gateway is reachable:Production Monitoring
Verify gateway connection in production:Configuration
The bot uses these config values:Troubleshooting
Gateway Not Running
Error:Connection failed: Cannot connect to host 127.0.0.1:18789
Solution: Start the OpenClaw Gateway:
Wrong Port
Error: Connection timeout or refused Solution: Verify the gateway port:Firewall Issues
Error: Connection timeout Solution: Ensure port 18789 is open:See Also
- Trigger Command - Quick call triggering
- Status Command - System status
- Server Command - Start webhook server
- OpenClaw Gateway - Official OpenClaw documentation