Skip to content

GPT-6.1 Sol vs Opus 5.5: Complaints Fact-Checked

Updated October 13, 2026 · first published October 13, 2026

Quick answer: Two sets of complaints are running at once. On the OpenAI side: Pro $200 got cut, GPT-6.1 Sol feels worse, Astra eats the allowance. On the Anthropic side: Claude Code limits shrank, Opus 5.5 burns...

Two sets of complaints are running at once. On the OpenAI side: Pro $200 got cut, GPT-6.1 Sol feels worse, Astra eats the allowance. On the Anthropic side: Claude Code limits shrank, Opus 5.5 burns the weekly cap, Opus 5.5 got nerfed. We took each claim and checked it against the vendors' own pages, Artificial Analysis, the GitHub issues people filed with numbers, and our own logs. Most of the money complaints hold up. The "it got stupid" complaints do not have evidence yet.

The short version:

Which complaints hold up?

ComplaintVerdictEvidence
OpenAI halved Pro $200True20x to 10x Plus on Oct 30, GPT-6 Pro chat 200 to 100 a week. Reported by several outlets and an OpenAI email quoted on Hacker News. We could not open OpenAI's help page (it returns 403 to our fetcher).
Claude limits were cutTrue and falseAnthropic's support page: +25% over pre-promo, permanent. Anthropic's own wording: a 17% reduction from the boosted level.
Opus 5.5 burns the weekly capMixedOne user measured 3.1x faster burn after the Sep 25 reset. Others report using 1% to 20% of a plan. Workloads differ and are unstated.
Opus 5.5 was nerfedUnprovenNo official confirmation, no status-page quality incident (Sep 1 to Oct 7), one independent test with no drop so far.
GPT-6.1 Sol is stupidUnprovenArtificial Analysis scores it one point below Astra. One user calls it "a train wreck in my project". No shared task.
GPT is cheaperTrueList prices, Artificial Analysis cost per task, and our own logs all agree.

What did Anthropic change in the Claude Code limits?

The weekly Claude Code limit moved three times in five months. Anthropic ran a 50% boost from May 13 to September 13. From September 14 the limit is 25% above the level before the boost, and Anthropic says that is permanent. Indexing the pre-boost limit at 100, it went 100, then 150, then 125. That is a drop of 16.7% from where users stood in early September, which Anthropic itself called a 17% reduction when it announced the change on August 29. The five-hour limits were not touched.

DateClaude Code weekly limit (pre-promo = 100)
Before May 13, 2026100
May 13 to Sep 13, 2026150 (temporary boost)
From Sep 14, 2026125 (permanent)
Sep 22, 2026Opus 5.5 launches; reported higher 5-hour limits and a one-off reset that expires Oct 22

Anthropic publishes no hours or token caps for any plan. Its pricing page says only that Max 5x and 20x are 5x and 20x Pro per five-hour session, with a weekly cap on top, and that Max has a separate weekly limit for Fable models. Any "hours per week" figure you see is third-party. We found no official October change to Claude limits or prices.

What does each model cost per token?

These are list prices per million tokens, read on each vendor's own pricing page on October 13.

ModelInputCached inputOutput
GPT-6 Astra$10$1.00$50
GPT-6.1 Sol$2$0.10$10
GPT-6 Sol$2$0.20$10
GPT-6 Luna$0.10$0.01$0.50
Claude Fable 5.1$10$0.25$50
Claude Opus 5$5$0.50$25
Claude Opus 5.5$4$0.20$20
Claude Sonnet 5.5$2$0.10$10
Claude Haiku 5.5 (prompts to 100K)$0.10$0.01$0.50

Three details change the bill more than the headline rate:

How much does effort level change the cost?

Effort is the biggest lever and the least discussed one. Both models take five levels: low, medium, high, xhigh, max. Both default to medium. Artificial Analysis ran both across its Intelligence Index and published score and cost per task for every level.

EffortOpus 5.5 scoreOpus 5.5 $ / task6.1 Sol score6.1 Sol $ / taskOpus costs
low42$0.5542$0.134.2x
medium51$1.3448$0.216.4x
high54$1.8250$0.325.7x
xhigh56$3.4651$0.398.9x
max58$5.9852$0.728.3x

Three readings of the table:

Our own coding measurements sit at the low end of that range: GPT-6 Sol needed 3.3x to 4.2x fewer dollars than Claude per task in our cost-per-task article. A general benchmark index and a coding workload will not match exactly, but the direction and the order of magnitude agree.

What do the Codex plans actually give?

OpenAI's pricing page lists local Codex messages per five-hour window on Plus, and the model you pick moves the number a lot:

Model on PlusMessages per 5 hours
GPT-6 Luna350 to 3,000
GPT-6.1 Sol15 to 160
GPT-6 Sol15 to 150
GPT-6 Astra5 to 45

Astra gets three to four times fewer messages than Sol, against a 5x price gap. That fits the "Astra drained my window" complaints without any nerf: the allowance is simply denominated so that the expensive model costs more of it. One Hacker News user wrote that Astra uses about 7x the allowance of 6.1 Sol in his testing. That is one person with no stated workload, but it sits in the same range. The pricing page also states that Fast mode draws 2.5x included usage and Ultrafast 8x. Pro plans currently carry no five-hour limit, only a weekly one, and OpenAI publishes no token budget for any tier.

What did people measure themselves?

We looked for people who posted numbers instead of feelings. The useful ones are on GitHub, in the anthropics/claude-code issue tracker. We could not read Reddit or X, so those threads are not covered here.

IssueClaimMethod and caveat
#97398 (Sep 26)Weekly burn rose after the Sep 25 reset: 93 responses per 1% before, 30 afterLocal transcripts, deduplicated. That is 3.1x on the user's own figures, though the title says 3.6x. One user, one workload.
#97074 (Sep 25)Headless claude -p burns about 1.8x more of the five-hour window per token than interactiveAbout $1.6 per 1% headless against $3.0 interactive. Same workload.
#98679 (Oct 1)Opus 5.5 median thinking tokens 67, then 126; median output 447, then 711Small sample (8 sessions in the second period), and the CLI version changed at the same time.
#96241 (Sep 23)Ultracode used 70% of a Max 5x plan in 20 minutes18 agents running at once. One anecdote with a number.

The first and third point the same way: more tokens per request drains the weekly cap faster. They are different users and different mechanisms, so treat that as a loose match, not a replication. On the other side, Hacker News commenters report using at most 1% of a $20 weekly limit for a code port, or never passing 20% of a plan. A 1% reading and a 54%-of-Max-in-two-days reading are both probably true. The workloads are not the same.

Is anyone testing for a nerf?

One project is. Livenerf runs a frozen panel of 78 questions with 90 samples a day for 30 days. On October 11 it was on day 18 and had published only its baseline: no drop detected. Its own documentation says it can detect a change of about 6.6 points per 10 days, and that it could not tell Opus 5 from Opus 5.5 at 99% confidence. So "no drop" does not prove "no nerf". It rules out a large one.

Anthropic's history is the other relevant fact. Its April 23 postmortem named three real causes of Claude Code quality complaints: default effort cut from high to medium (Mar 4 to Apr 7), a bug that cleared thinking history every turn (Mar 26 to Apr 10), and a prompt that capped replies at 25 words between tool calls (Apr 16 to Apr 20). The thinking-history bug probably also drained limits faster, through cache misses. Anthropic reset limits for all subscribers. So "it feels worse" was right in the spring, and the cause was configuration, not a quieter model. That is why we would check the effort setting and the client version before blaming the weights. The Anthropic status page shows no quality incident between September 1 and October 7; the entries are errors, latency and a spend-limit bug.

For GPT-6.1 Sol the picture is thinner. OpenAI says it scores near Astra at one fifth of the token price, and Artificial Analysis puts it one index point below Astra. The complaints we found are single posts, and several early "nerf" posts were about GPT-6 Sol, before 6.1 shipped on September 29. See why silent downgrades break your cost model for what a real regression test needs.

How should you check your own plan?

  1. Log the percentage, not the feeling. Codex writes used_percent and token counts into ~/.codex/sessions/. Price the requests at list rates, then divide dollars by percentage points used and multiply by 100. That is your dollars per window, the method behind our 60-day comparison.
  2. Record effort and client version with every reading. Issue #98679 shows why: a version bump and a date change look identical in the data.
  3. Keep interactive and headless runs separate. Issue #97074 measured 1.8x between them.
  4. Compare at equal effort. Medium against max is a 5x to 8x swing on either model.
  5. Re-measure after every reset or launch. Both labs moved limits around model launches this autumn.

What we could not verify?

Sources

Related


Want this applied to your stack? Bring the provider bills, gateway logs, and top workflows; we will map the cost drivers and savings path. Book a free audit →

Back to finopsllm.com