What’s shocking about it? Seems like the usual culprit— a bad config rollout. Took a long time to identify, so maybe that’s shocking. But I can attest that sometimes, you get into fight or flight mode and miss the obvious when trying to diagnose a disruption like this.
That said, nowadays, the first thing I do is spawn an agent to look through the most recent commits and try to identify something that could be the cause of a service outage.
This one seems like something Claude Code or Codex would have quickly flagged.
Agreed, we've all been there, but 4 hours! For a network config change. No one raised their hand and said "hey I just toggled this thing maybe we should look, I did it exactly when our entire region went had down"
Has any harness matched the effectiveness of Claude Code yet? I haven't experimented much recently, but every time I have in the past, I wasn't able to get any other tool to approach how effective I am in CC.
I'd love to use a different harness-- ideally an OSS one-- and hook it up to whichever LLM provides the best bang for the buck rather than being tied to Claude.
OpenCode has been great in my experience. I still get the best results using it with Anthropic's models, but some of the open weights ones are catching up (GLM 5 works reasonably well for me).
reply