ClawICU
OpenClaw Emergency Rescue
Diagnose failures, stabilize processes, and revive your OpenClaw instance — all from one command. Like an ICU for your AI gateway.
curl -fsSL https://xagent.icu/r | shCommon Diagnoses
When OpenClaw exhibits these symptoms, ClawICU provides the diagnosis and treatment plan.
Config Corruption
Configuration file has invalid JSON5 syntax or is corrupted, preventing OpenClaw from starting
Plugin / SDK Failure
Plugin crashes at activation, uses deprecated API (api.config.get), or plugin-sdk module is missing
Gateway Offline
OpenClaw gateway not running on port 18789, all agent channels unreachable
Daemon Not Installed
launchd (macOS) or systemd (Linux) service not registered — won't auto-start on boot
Missing Credentials
Provider API keys (OpenAI, Anthropic, Google…) missing or empty in the credentials store
Version Mismatch
CLI and Gateway running different versions after an upgrade — gateway restart resolves it
Channel Policy Issue
Discord groupPolicy set to allowlist with requireMention=true causes DMs to be silently ignored
plugins.allow Empty
All discovered plugins auto-load without an explicit allow list, creating a security risk
System Rescue Protocol
A proven medical approach — from first symptom to full recovery
Triage
Rapid OpenClaw doctor scan. Detect plugin crashes, gateway hangs, and TypeError storms in under 30 s.
Diagnose
Run 20 independent check modules — config, gateway, plugins, SDK, credentials, daemon, ports, and more.
Treat
Targeted repairs: disable broken plugins, restart gateway, populate plugins.allow, rebuild daemon services.
Recover
Verify all systems, confirm gateway heartbeat, and restore normal operation with a full backup in place.
6-Phase Rescue Protocol
Follow our proven medical rescue process to restore your OpenClaw instance
Treatment Notes
- Identify macOS vs Linux
- Detect npm, Docker, Podman, or source install
- Create temporary working directory
- Initialize logging
Treatment Notes
- Run openclaw doctor with 30-second timeout
- Auto-kills if a broken plugin causes a hang
- Capture full diagnostic output to temp file
- Detects TypeError, unhandled rejections, API errors
Treatment Notes
- Config file JSON5 syntax validation
- Gateway health check on port 18789
- Plugin runtime & SDK API compatibility
- Credential presence for all AI providers
- Daemon service (launchd / systemd) status
- CLI vs Gateway version mismatch detection
- Port conflict check (skips openclaw itself)
- Node.js version, disk space, state directory
- Channel policy, env vars, exec-approvals
Treatment Notes
- Aggregate all diagnostic findings
- Classify by severity: fatal / warn / info
- Vital signs monitor: CRITICAL / WARNING / STABLE
- Generate prioritized issue list for repair
Treatment Notes
- Interactive menu: Auto / Quick / Full / Nuclear / Export / Quit
- Fully interactive even when piped from curl
- Auto mode: handles all detected issues automatically
- Quick mode: safe, low-risk repairs only
Treatment Notes
- Automatic backup before any changes
- Disable broken / incompatible plugins (non-destructive)
- Restart gateway to fix version mismatch
- Populate plugins.allow to remove security risk
- Post-repair openclaw doctor verification
Where do you need to go?
Everything you need to diagnose and fix issues quickly
Need Help?
ClawICU is open source. Check the documentation, or open a GitHub issue — the community is ready.
Ready to Rescue Your OpenClaw?
One command. Full diagnosis. Automated repair. Your gateway back online in minutes.
OpenClaw crashed? Hit Share SOS to X — post a rescue card with one click.