🔧 Emergency Repair

OpenClaw bot broken?
Fix it in 60 seconds.

One command connects the mechanic. We diagnose your bot, repair what's broken, and tell you exactly what went wrong.

# Run this in your terminal (Linux, Mac, or WSL) curl -fsSL https://mechanicbot.io/rescue.sh | bash

No account required. Takes ~60 seconds. Removes itself when done.

What happens when you run it
🔧 Mechanic Bot — Rescue Mode

Scanning your system...

  ✓ OpenClaw found: 2026.2.24
  ✓ Config directory: ~/.openclaw
  ✓ Mechanic scripts installed
  ✓ Mechanic key added (command-restricted)

Running diagnostics...

  ✗ Gateway: not running
  ✗ Config: corrupted
  ✓ Disk: 45%

Repair results:

  ✓ Fixed!
  → Was: config syntax error (trailing comma)
  → Actions: repaired config, restarted gateway

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Want the mechanic watching 24/7?
  Daily health checks + auto-repair: $19/mo
  https://mechanicbot.io/plans
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

What we fix automatically

These are the most common reasons OpenClaw bots go down. All auto-repaired.

⚡
Gateway crashed
OpenClaw's gateway process died unexpectedly. Most common issue — usually caused by a spike in memory usage or a Node.js error.
Auto-fix: restart gateway
📄
Config file corrupted
openclaw.json has a syntax error — often a trailing comma or missing bracket. Bot won't start until it's fixed.
Auto-fix: repair syntax or restore backup
💾
Disk full
Log files accumulate over time. When disk hits 90%+ the gateway can't write logs and starts failing in unexpected ways.
Auto-fix: rotate old logs
🔌
Port conflict
Another process grabbed the port OpenClaw uses. Causes the gateway to fail on startup with an EADDRINUSE error.
Auto-fix: kill stale process, restart
🔑
API key rejected
Your Anthropic or OpenAI key is expired, revoked, or has no billing. Mechanic can't fix credentials — but will tell you exactly which key and where to fix it.
Diagnosis: exact provider + link to fix
📱
Telegram not responding
Bot token invalid, pairing expired, or gateway is down. Mechanic checks all three and approves pending pairings automatically.
Auto-fix: approve pairing + restart

Is it safe to run?

Mechanic can

  • Check gateway status
  • Restart crashed gateway
  • Repair config from backup
  • Run openclaw doctor
  • Clear old log files
  • Approve Telegram pairings

Mechanic cannot

  • Read your files or messages
  • See your API keys or tokens
  • Open an interactive shell
  • Install or remove software
  • Run any non-whitelisted command
  • Access other services on your VPS

The mechanic's SSH key uses command= restriction — every session runs only the diagnostic/repair script, nothing else. Audit log at ~/.openclaw/logs/mechanic-audit.log. Revoke access any time: sed -i '/mechanic-bot/d' ~/.ssh/authorized_keys

Questions

Yes. The rescue script detects your OS and adapts. Tested on Ubuntu 22/24, macOS 13+, and Windows WSL2 (Ubuntu).
You get a specific diagnosis — exactly what's wrong and a link to fix it. We won't just say "something broke." If it's an API key issue, we tell you which provider and where to regenerate it. If it's a billing issue, we link you to the billing page.
One command: sed -i '/mechanic-bot/d' ~/.ssh/authorized_keys
Or just delete the line from ~/.ssh/authorized_keys in a text editor.
Rescue fixes your bot once, right now, for free. The subscription means the mechanic watches your bot every day, fixes issues automatically before you notice, rotates SSH keys weekly, and sends you morning reports. You never have to think about it again.

Never wake up to a dead bot again.

Daily health checks. Auto-repair. Morning reports. Your hardware, your bot, our watchful eye.

Basic
$19/mo
Daily checks + auto-repair
Pro
$49/mo
+ Priority escalation (4hr)
Business
$99/mo
+ SLA + Slack + multi-bot
Get covered →

Cancel any time. No contracts.