Gateways
Gateways are OpenClaw instances that run AI agents and execute tasks. Mission Control connects to one or more gateways to orchestrate agent lifecycles, monitor sessions, and sync agent configurations.List Gateways
Retrieve all registered gateways with connection status and health metrics.Response
Array of gateway configurations
Gateway ID
Gateway name (unique)
Hostname or IP address (e.g.,
127.0.0.1, gateway.example.com)Gateway port (default: 18789)
Redacted authentication token (shows
-------- or empty)Whether authentication token is configured
Whether this is the primary gateway
Connection status:
online, offline, degraded, unknownUnix timestamp of last successful health check (null if never checked)
Health check latency in milliseconds (null if unavailable)
Number of active sessions on this gateway
Number of agents registered to this gateway
Unix timestamp
Unix timestamp
If no gateways exist, Mission Control automatically seeds a default gateway using environment variables (
OPENCLAW_GATEWAY_HOST, OPENCLAW_GATEWAY_PORT, OPENCLAW_GATEWAY_TOKEN).Add Gateway
Register a new gateway connection.Request Body
Unique gateway name for identification
Gateway hostname or IP address
Gateway port (typically 18789)
Authentication token for gateway API (if required)
Mark as primary gateway (automatically unsets other primaries)
Response
Created gateway object (see List response for schema)
Update Gateway
Update gateway configuration or health metrics.Request Body
Gateway ID to update
New gateway name
New hostname
New port
New authentication token
Update primary status (unsets other primaries if true)
Update connection status (typically set by health checks)
Update last seen timestamp (set by health checks)
Update latency metric (set by health checks)
Update session count (set by sync operations)
Update agent count (set by sync operations)
Delete Gateway
Remove a gateway registration.Request Body
Gateway ID to delete
Health Check Gateway
Probe gateway connectivity and update health metrics.Request Body
Gateway ID to check (omit to check all gateways)
Response
Whether gateway is reachable
Round-trip latency in milliseconds
Additional health check details (gateway version, uptime, etc.)
Gateway Configuration
Environment Variables
Mission Control reads default gateway settings from environment variables:Primary Gateway
The primary gateway is used for:- Default agent spawning
- Configuration sync operations
- Health monitoring dashboard
Integration with OpenClaw
Mission Control communicates with OpenClaw gateways over HTTP:| Operation | Gateway Endpoint | Description |
|---|---|---|
| Spawn agent | POST /spawn | Start a new agent session |
| Control session | POST /control | Pause/resume/kill session |
| List sessions | GET /sessions | Query active sessions |
| Health check | GET /health | Probe gateway status |
| Sync config | GET /config | Read agent configurations |
Authentication
Iftoken is set, Mission Control includes it in requests:
Agent Synchronization
Mission Control can sync agent definitions from gateway configuration files:- Creates new agents not in Mission Control
- Updates existing agents with new configuration
- Returns sync statistics
Response
Session Management
Monitor active agent sessions across all gateways:Query Parameters
Filter sessions by agent name
Maximum sessions to return
Response
Control Session
Pause, resume, or kill a gateway session.Request Body
Session control action:
pause- Suspend session executionresume- Resume paused sessionkill- Terminate session immediately
Multi-Gateway Support
Mission Control supports multiple gateway connections for:- Load distribution: Spread agent execution across gateways
- Geo-distribution: Run agents closer to data sources
- Environment separation: Dev/staging/prod gateways
- High availability: Failover to backup gateways
Gateway Selection
When spawning an agent, Mission Control selects a gateway based on:- Agent config - If agent has
gateway_config.preferred_gateway - Primary gateway - Default if no preference set
- Load balancing - Future: route to least-loaded gateway
Monitoring & Observability
Health Check Automation
Mission Control automatically health-checks all gateways:- Frequency: Every 5 minutes
- Updates:
status,last_seen,latencyfields - Circuit breaker: Marks offline after 3 consecutive failures
Gateway Dashboard
View gateway status in the Mission Control UI:- Connection status (online/offline/degraded)
- Latency graph (last 24h)
- Active session count
- Registered agent count
Security Considerations
- Token protection: Tokens are redacted in API responses
- Admin-only: Only
adminrole can add/update/delete gateways - Network isolation: Use private networks or VPNs for gateway communication
- TLS: Recommended for production (configure reverse proxy)
Best Practices
- Use descriptive names -
prod-us-east,dev-local, etc. - Monitor latency - High latency (>500ms) indicates network issues
- Set primary wisely - Choose geographically closest or most reliable
- Regular health checks - Enable automatic health monitoring
- Backup gateways - Configure at least 2 gateways for production
Rate Limits
- Gateway operations: 100 requests/minute per API key
- Health checks: Manual checks limited to 1 request/10 seconds
- Session control: 10 requests/minute per session
Automatic health checks and sync operations run independently and are not rate-limited.