1. Architecture 1 2 3 4 5 6 7 ┌──────────────────────┐ A2A/JSON-RPC ┌───────────────

1. Production Cases Cleaning up a node Restarting a node Deleting an abnormal Pod Inspecting the cluster 2. Two Steps to Get Configured Step one: configure MCP. Hand this configuration to OpenClaw and it will set it up for you. 1 2 3 4 5 6 7 8 { "mcpServers": { "ops-mcp-server": { "baseUrl": "http://ops-mcp-server/mcp", "headers": { "Authorization": "Bearer xxx" } } } } Step two: install skills.

1. Introduction to OpenViking 1.1 Use Cases Problem How OpenViking Handles It Fragmented context Unified management with a filesystem paradigm: memory, resources, and skills all map to a viking:// virtual directory, so context is managed the way files are High token consumption L0/L1/L2 tiering: the L0 summary (~100 tokens) is

1. Configure hooks Configure hooks in openclaw.json 1 2 3 4 5 6 7 "hooks": { "enabled": true, "token": "xxx", "path": "/openclaw/hooks", "allowRequestSessionKey": true, "allowedAgentIds": ["*"] }, See https://docs.openclaw.ai/automation/webhook The token here must not be the same as the gateway’s token. 2. Sending a message 1 2 3 4 5 6 7 8 9 10 11 12 curl --location 'https://xxx.

1. Start the Container Set the image 1 export IMAGE=ghcr.io/openclaw/openclaw:2026.3.2 Generate a random token 1 openssl rand -hex 32 Set the gateway token 1 export OPENCLAW_GATEWAY_TOKEN=xxx This token is used for authentication on both the remote web UI and the local TUI. Set directory permissions 1 2 mkdir -p openclaw-home