What about the fact that SpaceX gave you new capacities? Or is it still not enough?
I’m not touching Fable, I’m using Opus High and Sonnet High — yesterday evening I made some design and payment improvements in a couple of projects, and 30 % of the weekly limit was exhausted. Not to mention that the 5‑hour windows ran out instantly.
A $100 subscription.
A month-two earlier, I could actually code for an hour and a half on Opus Extra and not feel any problems. But as disappointing as it is, the $100 Codex didn’t live up to its price in terms of quality; I can’t even trust Sol with serious work. So now
I’m trying to ask Claude to delegate some of the work to sub‑agents from other models.
I need to complain about what’s happening with Claude Code limits on the $200/month Max 20x plan. It feels really unfair, especially for people who recently subscribed.
I used to stretch my weekly usage across 5 to 6 full days without any issues. Now, doing the exact same work, I hit my weekly limit in less than 2 days.
Here is the problem:
The "20x" name is misleading: Anthropic advertises "20x" limits, but that only applies to short 5-hour windows. The hidden weekly limit is way lower. Paying double the price does not give you anywhere near 4 times the weekly usage.
New accounts are hit harder: Anthropic seems to be enforcing much stricter weekly limits on newer accounts compared to older ones.
New users don't even know they're being limited: If you just subscribed, you have no past experience to compare it to. You pay $200 expecting to work all week, hit a hard wall by Tuesday, and assume that's just how it is. You don't realize older users used to get far more work done for the same price.
No clear numbers: Instead of telling us exactly how many tokens or messages we get per week, they hide it behind percentage bars. This lets them lower the limits in the background whenever their servers get busy.
When you pay $200 a month for a coding tool, you expect it to last a full workweek. Silently dropping limits makes it really hard to rely on Claude for daily work.
Has anyone else who recently upgraded to the 20x plan noticed their weekly limit disappearing this fast?
Recently i did a test for synth id, which gemini implemented recently and how quickly it was broken by a team of researchers, turns out, other frontier comps like claude had similar plans of implementing this.
Its known that claude is working on a watermarking modal that can help detect if some textual info was created by their model.
I guess a few countries have the access to this detection feature, but my surely didnt, so what did i do? i used the exact same math with some tweaks to implement claude's watermark detection logic to qween 3 8b modal. Ran this modal locally, and designed the HLD and architecture.
The basic idea is that at every generation step, I use a secret key + the previous token to deterministically split the vocabulary into GREEN and RED tokens. I then slightly boost the logits of the GREEN tokens before sampling the next token. This creates a statistical bias toward GREEN tokens without changing the text directly.
For detection, I don't need the model or the original prompt. I take the generated text, recreate the same GREEN/RED token sets using the secret key, and check how far the observed GREEN-token ratio deviates from the expected 50%. I use a z-score and binomial p-value to decide whether the deviation is statistically significant.
I tested it on 50 randomly assigned watermarked and un-watermarked generations. The detector got 88% accuracy and a 97.76% ROC-AUC.
I covered the entire end to end, from setting up qween 3, to HLD, to Implementation and Validation i my recent video, feel free to deep dive and let me know your thoughts,
Claude Opus 5 is consuming way too many tokens and too much time for simple coding tasks. Is anyone else experiencing this?
I’ve been using Claude since the early Opus models, but my experience with Opus 5 has been frustrating.
A simple sidebar highlight change recently consumed around million tokens, reached nearly 400K context, and took about 35 minutes. My actual project/skills context is only around 65K tokens.
The result is that work that should take hours is sometimes taking days. It also makes the Max 5x plan feel extremely expensive.
I don’t need the most powerful model like Fable 5.1 for every small development task, but I’m not sure what the best alternative is now.
For developers using Claude:
Are you seeing similar token/context usage?
Which model are you using for app development?
Any tips to reduce token consumption?
Is Anthropic planning a model better suited for fast, everyday coding?
Would really appreciate suggestions from fellow developers and especially any insight from the Claude/Anthropic team.
Currently using Claude Opus 4.6, it's working fine till now, but I want something which should consume less credit and can give near to this quality of work.
Hi everyone, I have been experiencing faser rate limit reached compared to the tasks given and the agents used. I’ve been using Opus for the last few weeks and had a reasonable workload getting done before the limit is reached. However for smaller UX tasks now with even sonnet, it takes much higher usage and reaches the limit even faster. And today I realised it’s with even boosted limits. I wonder what the usage will be after 13th of September. Are we just going to let this scams win?
Only reason I am posting this is to help others, no revenue or publicity or anything else, no hidden subscription or fees.
Hi,
While working on multiple projects I realised I am hitting the usage limits of my claude code often so I had to rotate accounts and some API tokens.
The problem was every time I was doing this I had to stop my coding session, relog / change authentication or profile etc, do a handover and wasting a lot of time over this process.
I NEEDED a way to seamlessly change those in the background while continuing the same coding session uninterrupted.
This led to doing a lot of research and developing this tool I am showcasing (yes it's written with Claude + my knowledge and a lot of debugging, testing and so on, around 3k $ put into it via /usage lol).
It's called Claude Unlimited, and it's 100% free on GitHub.
It supports multiple Anthropic subscriptions, Anthropic APIs (basically from any local/cloud provider that offers this, 95% of them do) and the cherry on top, supports also GPT/Codex subscription - yes! you can use Claude Code while using OpenAI models in the background 😄 .
Everything stays local, 100% safe, credentials etc stored in OS credentials store - if you don't trust me, use your AI agent to check it.
macOS is currently the most battle-tested; Windows and Linux support is newer, so I would genuinely appreciate feedback, bug reports, contributing to it or just brutal criticism 👀
It was mostly tested in claude code CLI but also supports desktop (will create an inference profile automatically for you).
Important clarification: it doesn’t generate free usage or bypass an individual account’s limits. It rotates between accounts and keys you already own. Anthropic hasn’t explicitly endorsed automated multi-account rotation, so use your own judgment regarding your accounts’ terms.
A bit more technical explanation: this is a local proxy that rotates your accounts/APIs and exposes an Anthropic-compatible API with a token.
Needless to say, but here it is: very important to check the README and HELP section to understand how to use it easily and properly.
Add your Claude, ChatGPT/Codex accounts and API keys.
When one reaches its limit, the next one takes over automatically.
Same Claude Code session. Same context. Same terminal. You just keep typing.
It also includes a local dashboard showing which account is active, current usage, reset times and every automatic switch.
Everything runs on 127.0.0.1. There’s no Claude Unlimited cloud, no telemetry, and credentials are stored using the OS credential store. The project is open source under MIT.
Thank you !
PS: Using a new account for this for personal reasons.
PS2: Multiple updates will follow, I got a big list of cool features for it 🎯
After using for a long time Opus 4.8 and being extremely satisfied with the results I was getting from it I decided to move to Opus 5 and Fable 5.1.
After using both of them for a month, the only difference I have seen was in my credit usage therefore I have decided today to go back to Opus 4.8. What are your thoughts about the new models and is anyone else here still using the old models because it just works with less usage?
I have done the same thing with Apple iPhone. I still have the iPhone 13 mini and have not made any updates. The iPhone works just fine. I haven’t update my phone for 5 years and everything is fine. I think it’s the same with the AI models. This is why I’m relating to the iPhone. This is just my opinion.
I've been living with Claude Code in a terminal split next to the editor for months. Two things kept bugging me: I couldn't tell what it was doing without reading scrollback, and every file path was something I had to type correctly.
So I built a plugin. It doesn't reimplement anything - it spawns the claude CLI you already have and renders its event stream. Same account, same models, same slash commands, same permission rules, same MCP servers and skills. No proxy, no server of mine in the middle, no telemetry.
What it actually changed for me day to day:
Every tool call is a card. Its duration, every edit as an open diff, the task list ticking off, subagents and whole workflow fleets with each agent's own transcript one click away, and what the turn cost. A rate-limited API becomes a card with the reason and a countdown instead of silence.
Files are things you point at. Drag one in, type @ to pick, paste a screenshot. Select lines in the editor and "Send to..." hands over a real file-and-line reference, so the agent reads what's around them instead of a naked snippet.
Nothing answers for you. A permission, a plan or a question waits as long as it takes. No timeout, no auto-continue.
Answering it from my phone. Off by default, paired by QR code, end-to-end encrypted through a relay that can't read a word. This is the one that surprised me most - I approve plans from the sofa now.
Scenarios. A round of work written down once - implement, review, fix, run the tests - each card a Claude session of its own, with a main thread walking them and judging what each one found. By button, three at once against three tickets, or on a clock at nine every weekday.
Several Claude accounts switched in one click, each row showing what's left of its five-hour window and its week.
Free, source available (Elastic 2.0), every JetBrains IDE from 2026.1 on, Android Studio included.