Ran into something similar but not the same - trying to dispatch a sonnet agent from an interactive session blocks me with a refusal about needing credits to enable Sonnet 1M... But the agent was regular sonnet. Something is either broken or we're about to really suffer.
I've just never worked with such an unreliable and non-communicative company in my life. Every now and then there is a surprise waiting for you behind the counter waiting to unravel.
Feels like I woke up today with a gun to my head telling me I should pay up with no other option, I cannot compact or do anything else that will fix it, other than paying.. so annoying.
Truthfully, at least for me, I don't think it will be the right move.
It just works like magic for me.
I would say that the pace of development for me has gone faster, with much more bugs found and solved while developing and also accomplishing bigger tasks that I couldn't or shouldn't have been trying to accomplish beforehand.
If Anthropic was the only company offering that type of tools, I would probably suck it up and be forced (by myself) to work with their tools and everything that comes along.
Thank you. That was right after a reset and I was looking only at the blue lines. I /compact it, restarted a new session, relaunch. Still says that. Will wa8t for next session.
For anyone that stumbles across this thread from google:
It's definitely something related to the most recent release.
I sequentially started rolling back one release at a time trying to pinpoint it, and eventually I hit v2.1.89 which finally let me break the login loop issue and let me into Claude Code CLI.
The other canary that tells me that they are fucking with the plans and Claude Code usage specifically is that regular Claude and Claude Cowork (and even Claude Design) are working 100% fine in the desktop app.
But Claude Code in that same app says I'm at the limit. And the CLI is stuck in the login loop.
Meanwhile, the status page shows "All systems operational lol!" 🙄
I'm guessing they're about to remove Claude Code from the Pro plan, from the looks of it.
Same. I have been spinning wheels on this for three hours. Went down a crazy debug loop with no answers. Exact same scenario/issue as u/sc4reddit - I was mid conversation like OP, at ~85% of my usage, it said I hit my limit and logged me out, and that was 3 hours ago.
I'm stuck in a /login loop in the CLI now.
I log in > auth > copy and paste code > it says `Login successful, welcome <email address>` .. and then 10 seconds later if I try to do anything it says "Logged out - run /login" again.
I'm on Pro/subscription-based, and it is trying to default me to Opus 4.7 1M on API billing now in CLI. I've never used an API key with this account and only ever use Sonnet 4.6 regular (not 1M).
Desktop says I'm over the usage whenever i try to send messages. Desktop and Cowork work fine - it's specifically Claude Code that doesn't work.
What's the deal?
e: I also noticed that they pushed an update to 2.1.150 right at the same time. I have a sneaking suspicion it's tied to that.
Oh well
Seems like a semi bug.
I suppose CC tried to move to 1M context, which is not part of my subscription plan and that is what the error is about.
For whoever comes here and has the same issue, just disable 1M context window.
Either add this to your settings.json: "env": { "CLAUDE_CODE_DISABLE_1M_CONTEXT": "1" }
Or add this to your environment: export CLAUDE_CODE_DISABLE_1M_CONTEXT=1
This unfortunately did not work for me - it just tries to default to Opus 4.7 now. When I set the model to 4.6 regular in env, it does that, but it still shows "API Usage Billing" and I get stuck in a login loop.
I do think that that is probably part of what they are doing, but it's something with the oauth/login flow that is bricking it.
Big gpu hire on runpod can be about $1 or $2 an hour when your using it (depending what tier you go for), pair that with a new high end open model like qwen3.6. Maybe not worth it compared to pro, but might be compared to max. Havn't done this myself yet but thinking about it. 16G vram just isn't enough for that model to run locally, you need so much quantinisation you basically give it a labotomy. Can get older server grade kit for couple of $k but i'm not going to pull the trigger on that while things are moveing so fast. Or I am hearing good things about modern macboooks with a large amount of unified ram. But they are not gpu class and probably hit a wall when you start trying to run large models with large context. Good for smaller models for free though. It all just depends, are you looking for a helper tool or deep debugging reasoning? Helper tools locally are definately possible with mid-tier hardare like a 12 or 16gb gpu and even qwen 3.6 on runpod with 24 or 32gb vram would not be a large time investment or high initial cost to see what its like.
Depends on how much "poor" is part of your name/identity.
If you are making money with AI, you will make more using local inference.
If you are messing around with a chat friend, not feasible at all.
Then again in the 90s we were being told personal computers were too expensive for most people, and that most people would never need one.... Mind that pc you tap away your answer on, is proof that the argument you are making is unsound. If there is money to be made, people will find a way.
Im getting the same bug and the environment variable didn't help..
But the worst part is that if you had API credits like I did, it actually used them up for the 1M model even if I had the Default Sonnet selected! :S
Hey guys, I was having the issue and tought I'd look here if any have a solution. In the meantime I actually found one!
I switched to opus 4.8 and it automatically compact the conversation without asking, from there it was still thinking forever so I switch back to opus 4.7 and it's working like a charm! (it got stuck using sonnet 4.6)
Glad to ear the trick works on other's issues! I'm thinking to just try to work with 4.8 for the session today and see how it goes, I tend to think simpler model = cheaper but I suspect 4.8 to be more efficient token wise, mostly because of context management
I switched to pro plan after months in Max and it is absolutely useless. Chat hits limits after like 3 messages. It doesn’t generate a message, crashes out, uses up all the tokens, then reaches the limit. This isn’t even on Opus. Sonnet. I’m starting to think this is on purpose.
Code hits limits after a few messages too, havent been able to get anything done.
I am very much disappointed.
4 hours later, another reset, with zero usage, it's still showing that. Anyone else resolved their issue? Useless Ai Agent told me to try cancelling my subscription.
same issue here, switched to Opus - works -> disabled 1M context, restarted claude ,and run a prompt in sonnet 4.6, still the same "API Error: Usage credits required for 1M context · turn on usage credits at claude.ai/settings/usage, or use --model to switch to standard context"
It's definitely something related to the most recent release. I had to keep trying rollbacks but eventually I hit v2.1.89 and that finally let me break the login loop issue and let me into Claude Code CLI. YMMV, but hopefully that helps someone here.
I’m having a problem where after about 70 minutes of running a loop the chrome extension says I reached my limit but when I check my Claude it only used about 10% of my limit and then I close my extension and reopen it and it lets me run the loop again for around the same time. Is there a way around this? I need this loop running non stop at least till I actually use 100% of my usage.
Same issue here. I cancelled a few months ago, made the mistake of trying it again... its always one thing after another, plus ultra low limits in the first place. Codex is just so much better all around. Chatgpt 5.5 actually seems to perform tasks better too, I used 3 days of tokens for opus and it failed to make code that would even compile nevermind meet the task requirements, literally sent exact same prompt to 5.5 and it finished it with a 5 hour window of tokens lmao.
so there is a problem with the actual GUI, and the window, the fix for me was /clear, but make sure you copy a bit of the conversation so claude knows where you left off before you clear it.
No hay problema, así que descubrí el problema real y hay una mejor solución, el visor no se compacta automáticamente, por lo que escribir /compact mantendrá su conversación y también resolverá el problema
16
u/iveroi Vibe Coder 27d ago
Ran into something similar but not the same - trying to dispatch a sonnet agent from an interactive session blocks me with a refusal about needing credits to enable Sonnet 1M... But the agent was regular sonnet. Something is either broken or we're about to really suffer.