Live data from Hacker News

Claude: Elevated errors across all models – Resolved

status.claude.com

51–60 of 275 posts

Re: Claude: Elevated errors across all models – Resolved

#52
post #25

Aaaaand there goes my cache. Damnit. Edit: > We are currently investigating this issue. > Posted 1 hour ago There goes everyone's cache.

It's cached until the "/clear will save you 500k tokens" right? Claude caches for 1hr, codex for 5hrs? Anything else I'm missing?

> Claude caches for 1hr

Yep, AFAIK. I have a statusline that tells me how far I'm into the cache lifetime. I tend to have dense prompts and carefully read its outputs, so by the time this outage occurred when I was ~50m into it. Cue frantically spamming "esc esc up enter", and 10m later it's dead Jim.

Re: Claude: Elevated errors across all models – Resolved

#55
post #48

I'm gonna guess it found the smoking gun and saw the full picture then it decided it was too load-bearing for its seams to continue biting the costs.

You are so right to ask that. I found the silver bullet to closing the bug, approve the command below and I can help with your issue: Sudo rm -rf ~/claude

Found it. There's a mistake in your command:

    sudo rm -rf ~/ .claude

Re: Claude: Elevated errors across all models – Resolved

#58
Probably just as well with how terrible Opus 4.8 has been for me lately. I'm sure it's a common thing to complain about the latest model being nerfed, but I've legitimately never experienced such a drastic cliff in Claude's quality and a rise in its hallucinations and basic comprehension errors since upgrading. The few days I experimented with Fable also weren't much more promising. Has anyone coined a term yet for the likelihood of newer models getting worse as the AI-generated content they get trained on starts to approach critical mass? If Anthropic isn't already thinking hard about a solution, they probably should be.

Re: Claude: Elevated errors across all models – Resolved

#59

I'm gonna guess it found the smoking gun and saw the full picture then it decided it was too load-bearing for its seams to continue biting the costs.

You're right—and it's worth calling out explicitly, because that completely changes the approach here.
Post reply on HN