Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Monitor OpenClaw gateway health with a watchdog state machine, Discord alerts, cooldown dedupe, and isolated fallback deployment on macOS. Use when users wan...
Monitor OpenClaw gateway health with a watchdog state machine, Discord alerts, cooldown dedupe, and isolated fallback deployment on macOS. Use when users wan...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Discord-first watchdog for OpenClaw gateway incidents.
Tell OpenClaw: "Install the gateway-watchdog skill." The agent will handle the installation and configuration automatically.
If you prefer the terminal, run: clawhub install gateway-watchdog
Watchdog data is isolated under ~/.openclaw/watchdogs/gateway-discord/. No edits to openclaw.json are required. Default mode is read-only monitoring (GW_WATCHDOG_ENABLE_RESTART=0). Automatic restart is opt-in and bounded by max attempts.
scripts/gateway-watchdog.sh - health checks + state machine + Discord notification. scripts/install-launchd.sh - installs a user LaunchAgent from template. references/com.openclaw.gateway-watchdog.plist.template - launchd template. references/cron-agent-turn.md - isolated cron prompt template.
The watchdog checks: openclaw gateway status --json openclaw health --json --timeout <ms> Pass criteria: gateway runtime is running RPC probe is healthy (when present) health snapshot returns successfully Failure classes: runtime_stopped rpc_probe_failed health_unreachable auth_mismatch config_invalid
bash "{baseDir}/scripts/gateway-watchdog.sh" Optional env: export DISCORD_WEBHOOK_URL="https://discord.com/api/webhooks/..." export DISCORD_BOT_TOKEN="discord_bot_token" export DISCORD_CHANNEL_ID="<your_discord_channel_id>" export GW_WATCHDOG_SOURCE="manual" export GW_WATCHDOG_FAIL_THRESHOLD=2 export GW_WATCHDOG_COOLDOWN_SECONDS=300 Delivery priority: DISCORD_WEBHOOK_URL DISCORD_BOT_TOKEN + DISCORD_CHANNEL_ID
Install LaunchAgent (does not edit OpenClaw core config): bash "{baseDir}/scripts/install-launchd.sh" --interval 30 --load Check status: launchctl list | rg "com.openclaw.gateway-watchdog"
Use isolated job and keep messaging in one channel: openclaw cron add \ --name "gateway-watchdog-internal" \ --cron "*/1 * * * *" \ --session isolated \ --message "Run bash {baseDir}/scripts/gateway-watchdog.sh and report state changes only." \ --announce \ --channel discord \ --to "channel:<your_channel_id>" \ --best-effort-deliver
Enable bounded restart: export GW_WATCHDOG_ENABLE_RESTART=1 export GW_WATCHDOG_MAX_RESTART_ATTEMPTS=2 Safety constraints: restart only after failure threshold is met max attempts enforced per incident window no reinstall or destructive mutation
state file: ~/.openclaw/watchdogs/gateway-discord/state.json state backups: ~/.openclaw/watchdogs/gateway-discord/backups/state-*.json event log: ~/.openclaw/watchdogs/gateway-discord/events.jsonl The script rotates old backups and keeps recent history for rollback/debugging.
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.