Let me read this rather than answer from memory.
Let me check instead of handwaving the details.
Let me confirm rather than blindly trusting.
Let me ground it in evidence rather than guess.
Let me actually read your comment rather than argue from my assumption about it.
> No agents are running; the three that were died on server-side errors
> Agent "[REDACTED]" failed: Agent terminated early due to an API error
> Fourth straggler from the same batch, same 529 ... That's all of them now — no agents left running.
> Agent "[REDACTED]" failed: Agent terminated early due to an API error
> Fifth and last straggler, [REDACTED], same 529, also died while still reading. ... That empties the queue. Still holding.
> Agent "[REDACTED]" failed: Agent stalled: no progress for 600s
> Sixth, [REDACTED] — stalled on the stream watchdog rather than a clean 529, same root cause. ... Six agents down, all from the outage. Nothing running. Still holding.
> Agent "[REDACTED]" failed: Agent stalled: no progress for 600s
> Seventh, [REDACTED], same stall. ... That accounts for the whole fan-out.
Does it, Claude? Does it actually account for the whole fan-out? It did, but I was still amused at the 4 successive no-more-agents messages I got back.
thought I saw 99.36% and 99.35% more than an hour ago - now it's up at 99.43%
edit: funny thing, my phone shows 99.29% uptime for "claude.ai" while my PC shows 99.43% at the same time (2x Firefox).
edit2: seems like the percentage changes based on the width of the screen
Every five minutes, check https://status.claude.com/. If the issue has been resolved, resume the Claude sessions running in the tmux sessions named session2, session3, and session7
Its automated with voice mode, so i dont even need to write commands, click a button say on voice + use a picker to select which terminals to do this for , Boom Done ,
I use it for other interesting scenarios too
All kidding aside, there's a part of me who wouldn't even be mad if AI just disappeared, I miss the pre-AI world
If we could go back to about 1994 tho when all I had was a mostly dumb cell phone, that'd be great. I do miss that world.
But for those who learned to code because they loved it at first sight this must be demoralizing.
Someone tell me how to ChatGPT my VSCode! ;)
Eternal September from here on, ie now the masses are using AI as much as me and we have supply crunch for the next 7 years....
[1] https://platform.claude.com/docs/en/about-claude/pricing
(Although notably this hurts people who got started using their quota but are under pro-rata rate. Which at present I am very not.)
I finally went from Pro to Max after hitting another 5 hour session limit today.
I love how people can share moments even though they are not close to each other physically at all. Imagine the cats outside could somehow connect with the cats in the other side of the world. No other animals can do this. Maybe whales, it depends how you define connect.
We are just gifted to live in such times.
Edit:
> We are currently investigating this issue.
> Posted 1 hour ago
There goes everyone's cache.
Anything else I'm missing?
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.
Let’s say I’ve already worked on something, so the KV cache is already there. If I use /clear, I’ll have to do that work again.
And yes, the KV cache will remain available for one hour, but who knows when this claude api will recover? We might forget about it, and when we come back after an hour—boom - we’ll be charged for cold writes.