Anthropic

I already run OpenClaw on my server. It handles the useful day-to-day layer: Telegram conversations, scheduled jobs, notifications, research, summaries, and the accumulating collection of small automations that make a personal assistant worth having. So at first glance, Claude Code Remote Control looked redundant. Why put another AI interface on the same box when I can already talk to OpenClaw from my phone? Because they solve different problems. OpenClaw is my normal control plane. But when an OpenClaw update breaks that control plane, I need an independent way back in. In the past that meant SSH from a laptop with the right keys. Fine at a desk; useless when the laptop is shut, elsewhere, or simply not with me. ...

At the end of March, my OpenClaw setup hit an awkward wall. For a while, Anthropic OAuth access had been good enough for day-to-day agent work. Then access tightened. I do not mean “the model got slightly slower” or “one request had to retry”. I mean the system became unreliable enough that I was pushed toward the API path. That sounded fine in theory. In practice it turned the assistant from a predictable tool into a metered engineering problem. ...

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. ...