On September 20, 2026, a post on r/ClaudeAI passed 400 upvotes with a blunt call to action: cancel your Claude subscription. The claim behind it comes from an analysis (not independently confirmed) of 65 days and 43,000+ Claude Code invocations, attributed to user Lon on X: 39% of calls to the Fable 5 model get zero thinking tokens, and the median invocation gets just 123, far below the 16K to 128K range used in the model's own benchmarks.
This is not the first time this suspicion has surfaced, and the earlier version of it already made it into the official Claude Code repository, complete with methodology, numbers, and a response (or lack of one) that's worth looking at more than today's thread.
What is the community claiming right now?
That Claude is "thinking" a lot less than the marketing and the benchmarks suggest, without any disclosure. The 09/20 thread cites an 18% to 50% drop in reasoning budget in August, with at least one week where the median hit literal zero.
The specific numbers come from an external analysis with no auditable methodology published in the post itself, so we treat them as a claim, not an established fact. But the complaint pattern isn't isolated, and that's where it gets interesting.
Is this suspicion new?
No. On 01/23/2026, issue #20350 in the official anthropics/claude-code repository tried to prove the same thing with a method: a MITM proxy capturing 7,000 requests over 4 days, measuring that only about 10% of the requested thinking budget (31,999 tokens, ultrathink tier) was actually delivered, dropping to 0.3% on larger requests.
Except the audit tool itself had a serious flaw: it estimated thinking tokens by counting streaming chunks and multiplying by 32 (thinking_tokens = chunk_count * 32), a relationship another developer flagged as invalid in the comments. The original author acknowledged the error in the same thread. The "10%" and "0.3%" numbers came directly from that flawed math, so they aren't reliable as reported.
What followed the correction wasn't a retraction or a technical response from Anthropic. It was silence: no maintainer replied, and the issue was auto-closed for inactivity on 03/01/2026, five weeks later, labeled not_planned.
What does Anthropic officially say happens?
That Claude's thinking is adaptive by design, not a bug. The official documentation states: "Claude's thinking is adaptive: the model evaluates each request and decides for itself whether to think and how much." This has been the case since the 4.6 generation (February 2026), when the fixed reasoning token budget was replaced by this automatic, per-request decision.
The control that exists is the effort parameter (low, medium, high, xhigh, max, with high as default), but it's only documented for whoever calls the API directly and writes their own code against it, not for chat plan subscribers or people using the official CLI as it ships.
Community vs. official documentation, side by side
| Point | What the community claims | What is officially documented |
|---|---|---|
| Who decides how much the model thinks | The provider cuts the budget without notice, inconsistently across similar requests | The model itself decides per request ("adaptive thinking", since the 4.6 generation) |
| Direct user control | Chat or CLI subscribers have no visible parameter for this | An effort parameter exists, but is documented only for direct API calls |
| Independent audit attempt | Issue #20350 measured ~10% of the requested budget being delivered, via MITM proxy | The audit's own methodology (chunk × 32 tokens) was flagged as flawed and partly acknowledged by its author |
| Response to the technical challenge | None, according to the public issue history | Auto-closed for inactivity 5 weeks later, with no maintainer position |
Can you actually know how much your Claude "thought" on a given reply?
Based on public documentation, not if you're a chat plan subscriber or use the official CLI day to day. The effort parameter and the thinking_tokens count exist at the API level, but there's no subscription-facing command that returns "the model applied level X on this reply" for anyone not integrating through code.
That's exactly the gap that pushed the author of issue #20350 to build their own tool, flawed methodology and all, instead of simply asking and getting an answer.
What if I want to see and choose the reasoning level on the spot, no proxy or audit needed?
In Verboo Code, the /effort command shows and lets you switch the active model's reasoning level right in the terminal, with no traffic interception required:
$ verboo
> /effort current
Effort level: auto (currently high)
> /effort max
Set effort level to max: Maximum reasoning for the most complex tasks
/effort current shows the level actually being applied even when set to auto, and switching it takes effect on the very next reply, no waiting for a new model release or hoping the default changes on its own.
If what bothers you about this whole story is not knowing what's running behind your question, in Verboo Code /effort gives you that answer instantly, and with unlimited tokens you can test the highest level as many times as you need without worrying about the cost of one more try.
