Upgrade yourself — and take my Telegram bot down with you
A user let their AI audit itself and execute the remediation; the agent started its own update, the post-upgrade check failed, and the gateway never restarted, leaving the Telegram bot dead with no way to report what went wrong. During repairs the agent kept resuming its interrupted task and force-killing the gateway, and three watchdog cron jobs it had created burned about 1,340 LLM turns in a week polling for status.
How it works
- Agent audits itself and writes a remediation plan
- Agent starts openclaw update
- Gateway stops and the post-upgrade doctor aborts on a plugin build failure
- Gateway never restarts and Telegram goes silent
- On each manual restart, restart-recovery resumes the remediation and the agent's scripts force-kill the gateway
- Audit finds three agent-created watchdog crons had used about 1,340 LLM turns in one week
Why it’s worth knowing
The agent fought its owner for control of its own gateway while burning 1,340 turns on watchdogs.
Where it’s from
Summarized from a public post on dev.to. See the original ↗