Devops

I had already written one postmortem about an OpenClaw update going badly. Then I did the thing that postmortems are supposed to prevent: I took another beta update. This time the failure was unusually clean. The update installed exactly what the package registry advertised. The gateway did exactly what its safety checks told it to do. And the combination could not possibly converge. The result was a gateway that crash-looped forever, a doctor command that appeared to hang, and a local TUI frozen on “connecting”. Recovery did not involve restoring a backup or deleting data. It involved understanding why the release was impossible, refusing to downgrade past a database migration, and applying one temporary local patch. ...

This was the worst OpenClaw update I have had. Not because one command failed. That would have been easy. It was worse: Telegram disappeared immediately after the update, openclaw doctor could not repair it, the local TUI was broken too, the first workaround degraded the system, and the beta recovery path corrupted enough state that I had to bring in a standalone Claude session from outside OpenClaw to patch SQLite manually. ...

A few weeks ago I wrote about fixing OpenClaw after context bloat and bad model routing. Then I immediately made a related mistake in the opposite direction. I switched the default model to openai/gpt-5.4 and kept the context window at 32,000 tokens. I wanted to test the model on real daily workloads. What I got instead was a week of repeating myself, failing background jobs, and an assistant that felt like it had short-term amnesia. ...

I hit a very predictable failure mode in AI automation: I left the defaults alone for too long. Background jobs accumulated too much context, some of them were still landing on expensive models, and a couple of nightly tasks started timing out. The fix was not dramatic. It was mostly configuration discipline. This was not an OpenClaw bug. It was a bad operating posture. What Broke Four things were interacting badly. ...

I’ve been running an AI personal assistant (via OpenClaw) for a couple of months now. It checks my emails, sends me a daily news digest, prepares GTD rituals, tracks weather before my morning runs, and does a dozen other things automatically. Last week I noticed something off: I hadn’t received a daily email notification in a while. Not an error. Not a crash. Just… silence. The job was running. The logs looked fine. But nothing was arriving. ...