Gateway Guard

What This Skill Does

Gateway Guard, developed by runeweaverstudios, acts as the primary synchronization layer for OpenClaw gateway operations. At its core, the skill ensures that the authentication handshake between the OpenClaw agent and the gateway remains consistent with your local openclaw.json configuration file. It identifies and resolves common friction points such as token mismatches, password errors, and the frustrating device_token_mismatch alerts that can stall automated workflows. Beyond simple authentication management, it features an intelligent monitor for execution logs. When it detects an Unhandled stop reason: error within the gateway logs, it can be configured to auto-trigger a "continue" signal, effectively allowing agents to self-recover from transient errors without requiring manual intervention.

Installation

To integrate this utility into your OpenClaw environment, execute the following command in your terminal:

clawhub install openclaw/skills/skills/runeweaverstudios/gateway-guard

Ensure that you have sufficient permissions to modify the configuration files located in your OpenClaw directory, as the skill interacts directly with openclaw.json to ensure credential alignment.

Use Cases

Gateway Guard is most effective in high-uptime scenarios. Use it when:

• You encounter consistent "Gateway auth issue" or "unauthorized" warnings in your session logs.
• You are preparing to launch a complex orchestrator flow (e.g., using sessions_spawn) where a gateway failure at the start could disrupt downstream sub-agents.
• You have performed a recent update to OpenClaw and need to verify that your current gateway service is utilizing the most recent credentials.
• Your TUI session drops unexpectedly, and you need to reset the connection link between the daemon and the gateway.
• You are running long-term background tasks that occasionally trigger transient stop errors.

Example Prompts

• "Gateway Guard, please check the status of my current gateway connection and apply a fix if the token in my openclaw.json doesn't match."
• "There is an unhandled stop reason error in the gateway logs; please enable the continue-on-error loop to keep the agent running."
• "Verify that the gateway authentication is synchronized before I start the new batch of sub-agents."

Tips & Limitations

• The --loop parameter in the continue-on-error command is a powerful tool, but use it judiciously. Ensure your task logic is idempotent to prevent unintended side effects if the error persists.
• Always run status before ensure --apply to verify exactly what changes the script intends to make to your environment.
• If you notice a high frequency of device_token_mismatch errors, manually audit your openclaw.json structure, as frequent guard intervention might be masking underlying configuration drift.