Openclaw Self Healing

Status (2026-10-13): not actively maintained. Last updated 2026-07-25 and built against OpenClaw before 2.0 — not verified on OpenClaw 2.0 (2026.9+). Issues are read, but replies may be slow.

OpenClaw Self-Healing System

Autonomous crash recovery for long-running services

Stop getting paged at 3 AM. Let the machine try the obvious fixes first.

Quick Start · How It Works · Known Gaps · Docs

What this is

A set of shell scripts that wrap a long-running service with a five-level recovery ladder. A plain watchdog restarts a crashed process; that is enough right up until the crash is caused by something a restart cannot fix — a corrupted config, a missing key, a broken dependency. Then the restart becomes a crash loop and you get paged anyway.

This system adds two things a plain watchdog does not have: validation before start (Level 0) and an AI diagnosis session (Level 3) that reads the actual logs and config before attempting a repair. If both fail, it escalates to a human with the log paths attached.

It was built for OpenClaw Gateway and is tested against it. The architecture is not specific to OpenClaw — the scripts take the service command, port and paths from environment variables — but adapting it to another service currently means editing the scripts, not flipping a config switch.

Demo

*Recovery ladder in action: KeepAlive → Watchdog → AI diagnosis → Alert*

How it works

The five levels

What the installer actually wires up

This matters more than the diagram. The installer downloads all five scripts plus both shared libraries, but it only creates two scheduled units:

Compared to rolling your own

The gap that matters: when a crash loop is caused by something a restart alone cannot fix, every other tool pages you. This one tries to read the logs…