openclaw-guardian and openclaw-self-healing
These are **competitors**: both provide autonomous monitoring and self-repair capabilities for OpenClaw Gateway, with Guardian offering git-based rollback and snapshot management while Self-Healing emphasizes 4-tier recovery orchestration, making them alternative approaches to the same infrastructure resilience problem.
About openclaw-guardian
LeoYeAI/openclaw-guardian
🛡️ Guardian watchdog for OpenClaw Gateway — auto-monitor, self-repair via doctor --fix, git-based rollback, daily snapshots, and Discord alerts. Powered by MyClaw.ai
Implements a cascading recovery strategy with exponential escalation: failed health checks trigger automated repair attempts via `doctor --fix`, then escalate to git-based workspace rollback if repairs exhaust, with configurable cooldown periods to prevent thrashing. Integrates with OpenClaw Gateway's diagnostic tooling and operates alongside existing watchdog processes, offering complementary coverage through daily git snapshots and optional Discord webhook notifications for alert aggregation.
About openclaw-self-healing
Ramsbaby/openclaw-self-healing
AI-powered self-healing system for OpenClaw Gateway • 4-tier autonomous recovery • macOS & Linux
Implements LLM-agnostic root-cause analysis (Claude, GPT-4, Gemini, Ollama) that diagnoses and auto-fixes corrupted configs, rate limits, and dependency failures — preventing crash loops before escalation. The 5-tier architecture progresses from instant restarts through HTTP health checks to PTY-based log analysis and optional multi-channel alerts (Discord/Slack/Telegram), with Prometheus metrics for observability across macOS, Linux, and Docker deployments.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work