Hacker News Reader

Comment by ectoloph | Hacker News Reader

These bursts of downtime are one of the reasons I end up with multiple smaller subscriptions between providers.

I'd just end up being really annoyed about the downtime if it lands in the middle of a working day.

Not sure if it’s just me but in Codex, GPT-5.6-Sol and IIRC older 5.5 models can stop dead in the track a couple times a day saying “model is at capacity” (paraphrasing). Then I wait a minute or two and ask it to continue and it’ll more often than not happily use the same model. These frequent mini “outages” are pretty annoying especially if one isn’t supervising. Claude has had long outages but I haven’t run into this kind of mini outages on a daily basis recently.

That happens to me constantly with codex

I wish the harnesses would auto resume but I suppose that would also add more load without more money for subscription customers...

in the codex case, it will keep going it is not a blocking prompt.

OpenCode has an autoretry functionality (that progressively waits more after each failed request). I m surprised other harnesses don't have that.

I should have mentioned Claude Code, specifically. It sounds like other harnesses are better. I'm a bit entrenched with CC at this point since that's what we have a subscription to at work and they don't support other harnesses on subs

Hermes seems to pick up after a stoppage. At least I've never had to push it again, it might just take a long time to finish a task and then I'll see the messages in the transcript.

Reply on news.ycombinator.com