How do I install the Openclaw Self Healing skill?

Run npx skillmds@latest add dvcrn/openclaw-self-healing in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Openclaw Self Healing safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts, makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Openclaw Self Healing?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Openclaw Self Healing free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Openclaw Self Healing?

dvcrn (@dvcrn) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Openclaw Self Healing by dvcrn — Agent Skill

Name: Openclaw Self Healing
Rating: 4.2 (5 reviews)
Author: dvcrn

Openclaw Self Healing

4-tier autonomous self-healing and auto-recovery system for OpenClaw Gateway. Monitors gateway health, auto-restarts on crash, detects OAuth token expiry, kills zombie processes, and escalates to Claude Code AI for diagnosis when automated recovery fails. Use when your OpenClaw gateway crashes, stops responding, enters a restart loop, or needs automatic monitoring and recovery. Features watchdog, config validation, exponential backoff, Discord/Telegram alerts. macOS & Linux.

dvcrn Updated Sep 8, 2026 32 repo stars

File contents

OpenClaw Self-Healing System

"The system that heals itself — or calls for help when it can't."

A 4-tier autonomous recovery system for OpenClaw Gateway, featuring AI-powered diagnosis via Claude Code. Tested in production on macOS + Linux.

Architecture

Level 1: config-watch        → Config file change detection + instant reload
Level 2: Watchdog v4.4       → OAuth detection, zombie kill, exponential backoff
Level 3: Claude Code Doctor  → AI-powered diagnosis & repair (30 min window) 🧠
Level 4: Discord/Telegram    → Human escalation with full context

What's New in v3.1.0

Complete healing chain fix — config-watch → Watchdog → Emergency Recovery now fully connected
Installer rewrite — single install.sh covers macOS (LaunchAgent) + Linux (systemd)
Watchdog v4.4 — OAuth token expiry detection, zombie process auto-kill, Exponential Backoff
Emergency Recovery v2 — persistent learning repo, reasoning logs, multi-model support (Claude Code + Aider)
Metrics dashboard — success rate, MTTR, trending analysis via tmux

Quick Setup

bash <(curl -fsSL https://raw.githubusercontent.com/Ramsbaby/openclaw-self-healing/main/install.sh)

Or install via ClawHub:

npx clawhub@latest install openclaw-self-healing

The 4 Tiers in Detail

Level	Script	Trigger	Action
L1	`config-watch.sh`	Config file change	Validate + reload gateway
L2	`gateway-watchdog.sh`	Process down / HTTP fail	Kill zombie → restart → backoff
L3	`emergency-recovery-v2.sh`	30min continuous failure	Claude Code PTY diagnosis
L4	`emergency-recovery-monitor.sh`	L3 triggered	Discord + Telegram alert

Configuration

All settings via environment variables in ~/.openclaw/.env:

Variable	Default	Description
`DISCORD_WEBHOOK_URL`	(none)	Discord webhook for L4 alerts
`OPENCLAW_GATEWAY_URL`	`http://localhost:18789/`	Gateway health check URL
`HEALTH_CHECK_MAX_RETRIES`	`3`	Restart attempts before L3 escalation
`EMERGENCY_RECOVERY_TIMEOUT`	`1800`	Claude recovery timeout (30 min)

Verified Recovery Cases

OAuth token expiry — Watchdog v4.4 detects 401 in logs, restarts before agent dies
Zombie process — Preflight detects PID mismatch, SIGKILL + launchctl kickstart
Config schema error — openclaw doctor --fix auto-applied on exit_1 pattern
Level 3 triggered — Claude Code diagnosed and fixed broken config in < 15 min

License

MIT — built by @ramsbaby + Jarvis 🦞

---name: openclaw-self-healingdescription: 4-tier autonomous self-healing and auto-recovery system for OpenClaw Gateway. Monitors gateway health, auto-restarts on crash, detects OAuth token expiry, kills zombie processes, and escalates to Claude Code AI for diagnosis when automated recovery fails. Use when your OpenClaw gateway crashes, stops responding, enters a restart loop, or needs automatic monitoring and recovery. Features watchdog, config validation, exponential backoff, Discord/Telegram alerts. macOS & Linux.---# OpenClaw Self-Healing System> **"The system that heals itself — or calls for help when it can't."**A 4-tier autonomous recovery system for [OpenClaw](https://github.com/openclaw/openclaw) Gateway, featuring **AI-powered diagnosis** via Claude Code. Tested in production on macOS + Linux.## Architecture```Level 1: config-watch → Config file change detection + instant reloadLevel 2: Watchdog v4.4 → OAuth detection, zombie kill, exponential backoffLevel 3: Claude Code Doctor → AI-powered diagnosis & repair (30 min window) 🧠Level 4: Discord/Telegram → Human escalation with full context```## What's New in v3.1.0- **Complete healing chain fix** — config-watch → Watchdog → Emergency Recovery now fully connected- **Installer rewrite** — single `install.sh` covers macOS (LaunchAgent) + Linux (systemd)- **Watchdog v4.4** — OAuth token expiry detection, zombie process auto-kill, Exponential Backoff- **Emergency Recovery v2** — persistent learning repo, reasoning logs, multi-model support (Claude Code + Aider)- **Metrics dashboard** — success rate, MTTR, trending analysis via tmux## Quick Setup```bashbash <(curl -fsSL https://raw.githubusercontent.com/Ramsbaby/openclaw-self-healing/main/install.sh)```Or install via ClawHub:```bashnpx clawhub@latest install openclaw-self-healing```## The 4 Tiers in Detail| Level | Script | Trigger | Action ||-------|--------|---------|--------|| L1 | `config-watch.sh` | Config file change | Validate + reload gateway || L2 | `gateway-watchdog.sh` | Process down / HTTP fail | Kill zombie → restart → backoff || L3 | `emergency-recovery-v2.sh` | 30min continuous failure | Claude Code PTY diagnosis || L4 | `emergency-recovery-monitor.sh` | L3 triggered | Discord + Telegram alert |## ConfigurationAll settings via environment variables in `~/.openclaw/.env`:| Variable | Default | Description ||----------|---------|-------------|| `DISCORD_WEBHOOK_URL` | (none) | Discord webhook for L4 alerts || `OPENCLAW_GATEWAY_URL` | `http://localhost:18789/` | Gateway health check URL || `HEALTH_CHECK_MAX_RETRIES` | `3` | Restart attempts before L3 escalation || `EMERGENCY_RECOVERY_TIMEOUT` | `1800` | Claude recovery timeout (30 min) |## Verified Recovery Cases- **OAuth token expiry** — Watchdog v4.4 detects 401 in logs, restarts before agent dies- **Zombie process** — Preflight detects PID mismatch, SIGKILL + launchctl kickstart- **Config schema error** — `openclaw doctor --fix` auto-applied on exit_1 pattern- **Level 3 triggered** — Claude Code diagnosed and fixed broken config in < 15 min## Links- **GitHub:** https://github.com/Ramsbaby/openclaw-self-healing- **Changelog:** https://github.com/Ramsbaby/openclaw-self-healing/blob/main/CHANGELOG.md- **Linux setup:** https://github.com/Ramsbaby/openclaw-self-healing/blob/main/docs/LINUX_SETUP.md## LicenseMIT — built by @ramsbaby + Jarvis 🦞

Frequently asked questions