Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
gateway-guard 1.0.7 - No file or functionality changes detected in this release. - All documentation, descriptions, and behavior remain unchanged.
What This Skill Does
Keeps OpenClaw gateway authentication in sync with openclaw.json by detecting token and password mismatches. Can automatically send "continue" to a stalled agent when "Unhandled stop reason: error" appears in gateway logs. Invoke it before delegating to sub-agents or after updating OpenClaw.
Automates the check-and-restart cycle that would otherwise require manually inspecting logs, editing openclaw.json, and restarting the gateway each time auth drifts.
When to use it
- Diagnosing device_token_mismatch errors before spawning sub-agents
- Verifying gateway auth is correct after an OpenClaw update
- Auto-resuming stalled agent runs when a run error appears in gateway logs
- Restarting the gateway with the correct credentials when the TUI disconnects
- Checking gateway status at the start of an orchestrator flow
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: The TUI won't connect and logs show device_token_mismatch
- 1Run gateway_guard.py status --json to get current auth state
- 2Detect mismatch between running gateway credentials and openclaw.json
- 3Run gateway_guard.py ensure --apply --wait to restart gateway with correct credentials
- 4Confirm gateway port is open and status returns ok
Gateway restarted with credentials matching openclaw.json, TUI can reconnect