Coding is solved
Nothing to do with coding and everything to do with capacity. In fact, this proves that there is no AI Bubble and we are massively capacity constrained (aka we under-invested in infrastructure)
Elevated errors on Claude.ai, API, Claude Code
161–170 of 241 posts
Re: Elevated errors on Claude.ai, API, Claude Code
#162Have anyone found good techniques to get a session out of Claude Code, so that I can point another tool at it and pick up there? This always seems to happen at the worst possible time, after having spent an hour getting deep into something – half finished edits across files, subagents running, etc.
Re: Elevated errors on Claude.ai, API, Claude Code
#163Yea, it's peak time. They don't have enough compute. Why do you think they are banning external subscription use. They sell subscriptions. They don't need people to use CC. That doesn't matter. And yet - they won't have people using their service outside of CC. Something is fishy.
Maybe something to do with revenue growth being utterly insane and just not being able to keep up with demand.
Re: Elevated errors on Claude.ai, API, Claude Code
#164Have anyone found good techniques to get a session out of Claude Code, so that I can point another tool at it and pick up there? This always seems to happen at the worst possible time, after having spent an hour getting deep into something – half finished edits across files, subagents running, etc.
Honest suggestion - ask the agent to figure a compat shim out, the files are jsonl stored at your ~/.claude/sessions you can most likely just reshape it to work on OpenCode or similar, or have a different Claude Code config that points to OpenRouter or other API style endpoint CC supports and then you can swap accounts and it should still work!
I could search it myself, but haven't needed to. Getting it out of SQLite into some format Cursor understands should be trivial.
Re: Elevated errors on Claude.ai, API, Claude Code
#165Earlier quoted context omitted.
I can't sign in. We're not at capacity for OAuth servers or relational databases. This proves that vibe coding your infrastructure is a bad idea.
If you have this view in 2026 April, you are going to have a bad time
Re: Elevated errors on Claude.ai, API, Claude Code
#166Re: Elevated errors on Claude.ai, API, Claude Code
#167Re: Elevated errors on Claude.ai, API, Claude Code
#168Earlier quoted context omitted.
Maybe something to do with revenue growth being utterly insane and just not being able to keep up with demand.
I'm just saying - a better company would be more open about such issues. I'm paying for something I'm not getting. Does not seem reasonable!
Re: Elevated errors on Claude.ai, API, Claude Code
#169I just had to upgrade my plan because I ran out of tokens because medium effort had dementia and things only worked on high. Good to know I'm getting my money's worth...
Re: Elevated errors on Claude.ai, API, Claude Code
#170Earlier quoted context omitted.
maybe, but the response to GPU shortages being increased error rates is the concern imo. they could implement queuing or delayed response times. it's been long enough that they've had plenty of time to implement things like this, at least on their web-ui where they have full control. instead it still just errors with no further information.
Coding is a problem solved. Claud writes the code. I edit it. I code around it. Engineer roles dead in 6 months.
You're never gonna guess what software engineers do.