You are right to push back on this. I should be more explicit. My honest take is that this is, in fact, my honest take. I appreciate you holding me accountable here.
Honestly, you're right. I didn't listen to you and that's on me. And from now on, I'm going to tell you everything you need to know - no fudging, no white lies, no speculation, just the truth.
If anything Claude writes too many comments. Instead of clean code it dumps walls of text describing a given 'if' as a 'user-grained access-gated control-correcting flow-valve'.
You say Claude, I too would prefer not to read reams of comments or an essay everytime I revise the plan in plan mode, but do you know if any other tools are better than it? I've never used Codex, but I remember Claude Web's natural conversational approach being a welcome sight compared to ChatGPT's overly-formatted listicles.
My experience is Codex is much better but less creative. I use its agent through GitHub Copilot or the agent interface from JetBrains. Try the GPT Sol 5.6 on medium, it gives me good results
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
I do the same with deepseek-v4-flash + opencode triggering via mcp those terminals again by sending tmux keystrokes of Newline to those sessions and a custom setup i keep ready for these
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 rely so much on these, the ROI on having a max 90 claude plan + pro 90 codex plan is way higher than haing one solo 180 plan on a single one. It allows to derisk the issue, and also as they both kind of generous with quota reset when issues happens on their side, and it happens a lot, you get in the end way more tokens
Not that I've forgotten how to write code; it's just I'm not familiar with my vibecoded code base, and getting familiar + getting things done is probably going to take more time than for Claude to come back. I will go touch grass in meanwhile.
Out of my 7 simultaneous sessions (my usage limit reset is tomorrow, so I have some lesser important projects to use my tokens on) there is still 1 session purring on. So there's at least 1 little Claude server still running.
Claude always seems unreliably lately. Output and reasoning have become very inconsistent even on good days. I'm actually feeling more productive now that it's down.
They should sell an add-on to your subscription so that if Claude is down it routes the queries to OpenAI. Then OpenAI can do the reverse for their subscriptions, and if both are down, Grok will invest your portfolio into Nvidia.
The whole Opus family has exactly the same cost structure [1]. Since Opus 5 is smarter, you can use lower effort levels (= less tokens) making it cheaper to run than 4.8.
Another wakeup call to realize how desperately we need on-device LLMs to be fast and smart for daily use. Thankfully, every month there's progress made in that direction. Just imagine how your life as a developer would be if you had to use a cloud provider to run Python, and the provider's status page looked like the Christmas tree we see today.
Claude is back up. Just spoke with him about slinky, versatile femboys with cute feet. All good. Gonna pentest with Rust to pay for my fursuit at Defcon.
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.
Can we please stop posting here every time Claude or OpenAI are down? These are not critical services like AWS / S3 where downtime means that your application is offline. Nothing is easier than switching to another provider, mid-session even.
No this whole thread is such a nice thing to happen. It's like the lights are out on your building and you're joking about it with your neighbors when you're all just waiting for it to come back. But on a gigantic scale.
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.
So this is the technology that will underpin each and every facet of work, but it can randomly go down for hours with no accountability, and so do all of the services based on it.
But hey, AGI tomorrow.
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.
Sudo rm -rf ~/claude
“I’m tired, boss”
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.
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....
surely you mean SPCX
[1] https://platform.claude.com/docs/en/about-claude/pricing
I finally went from Pro to Max after hitting another 5 hour session limit today.
- read & respond to customer feedback
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.