Boris Cherny, the engineer who leads Claude Code at Anthropic, posted to Threads on Thursday evening April 16: "Opus 4.7 uses more thinking tokens, so we've increased rate limits for all subscribers to make up for it. Enjoy!" [1] The post — 935 likes, 62 reposts, 141 replies within 72 hours — is the first visible corporate concession since Anthropic released Opus 4.7 on Thursday night and the Reddit, GitHub, and X communities that the paper's Sunday coverage called "the unresolved mutiny" began documenting what they had documented with Opus 4.6: the new model burns more tokens per prompt, breaks existing API behavior, and empties rate-limit budgets faster than the prior model did. The paper's April 18 framing — that safety-as-branding and safety-as-revenue-constraint were the same bet — now has its operational data point. The revenue constraint is biting. The company lifted the ceiling without touching the price.

The technical architecture of Cherny's concession is more revealing than the concession itself. Opus 4.7 introduces three breaking changes Anthropic's own documentation names. [2] The model uses a new tokenizer — producing, on community benchmarks, 30 to 35 percent higher token counts for identical input prompts. Manual extended thinking — the budget_tokens API parameter developers used to cap reasoning token consumption on Opus 4.6 — is no longer supported; requests that send it receive a 400 error. Adaptive thinking is the only thinking-on mode. Setting temperature, top_p, or top_k to non-default values also returns 400. The model thinks more, uses a tokenizer that measures more, and offers developers fewer levers to control the cost. On a fixed-price subscription, the operational consequence is predictable: rate limits that used to carry an hour of coding now carry forty minutes.

The Reddit community — r/ClaudeAI, r/singularity, the Claude-Code subreddit — has been documenting the pattern in threads that run hundreds of replies. [3] The Fortune investigation published April 14 (before Opus 4.7 shipped) had already named the Opus 4.6 performance-decline complaints and the transparency accusations community members had been making for weeks. When 4.7 shipped, the community read it through that prior pattern: a model release accompanied by tokenizer changes that inflate reported token usage and produce rate-limit consumption that was not present in the prior version. The Anthropic documentation itself acknowledges that Opus 4.7 "uses a new tokenizer, contributing to its improved performance" and that "the token efficiency of Claude Opus is different" from what it "did for Claude Opus 4.6." [4] The acknowledgment is embedded; the concession from Cherny is the response to the community noticing.

What Cherny's post is not, and what the discourse the paper follows has been watching for, is a pricing change. Anthropic did not reduce prices. [5] Subscription tiers remain unchanged at Free/Build, Tier 1 (paid), Tier 2, Tier 3, and Tier 4/Enterprise. Rate limits are tier-dependent and measured per minute — requests per minute, tokens per minute, tokens per day. Increasing those numbers is a cheaper concession than reducing per-token pricing or refunding overages; it costs the company compute headroom at the margin, but it preserves the commercial architecture of the product. The Reddit response to Cherny's Threads post, archived on the daily.dev aggregator as the "rate limit bug fixed, limits increased for all subscribers" post on April 16, was split: appreciation from developers whose limits were biting, frustration from power users who noted that Max-tier advice had become "use Sonnet instead of Opus and lower the effort level" — the new operating guidance, in which the top tier is effectively told to stop using the top model.

The philosophical texture of the concession matters for what the paper's ai-state-power thread has been tracking since March. Anthropic's public identity is anchored in safety — Dario and Daniela Amodei built the company around a foundation-model safety story, and the brand defense is that Claude is both more capable and more careful than its competitors. But Claude's revenue comes from enterprise customers who price Claude against OpenAI and Google Gemini on throughput and cost per token. When the brand story produces a product that is more careful at the cost of more tokens per task, the brand story is taxing the revenue story. Cherny's concession lifts the tax by giving subscribers more headroom without acknowledging the shift in unit economics it documents. The post is on Threads, Meta's social platform, rather than on Anthropic's blog, status page, or Twitter/X account — a social-media concession to a community revolt, not a policy statement.

Cherny's adjacent Threads posts from the same thread document the broader guidance developers should absorb: "In Claude Code the default effort is now xhigh, a new level between high and max giving finer control over the reasoning/latency tradeoff. 4.7 thinks more, so token use runs higher than 4.6. Manage it with effort." [1] That is the corporate voice of the engineering team telling users that the token-inflation is not a bug. It is a feature. Users who do not want the feature can reduce the effort level manually, which produces a worse answer. The concession to the mutiny is that Anthropic will not charge users for the feature they did not ask for; the price of the concession is that users must now take responsibility for managing the model's effort allocation themselves. This is how a revenue constraint produces a governance feature.

The parallel thread — which the paper treats separately, and which a colleague covers in a different piece — is the European Central Bank's quiet opening of a supervisory dialogue on Anthropic's separate Mythos model. That is the bank-regulatory frame on frontier-AI cyber risk, a distinct vector from the subscriber-revolt dynamic. The two threads converge only at the level of the paper's April 17-18 framing of Anthropic as a company running a two-track week: safety-as-branding on one track, safety-as-revenue-constraint on the other, both visible in the same cycle. The Mythos supervisory dialogue is safety-as-governance-risk being absorbed into routine banking supervision. The Opus 4.7 rate-limit concession is safety-as-revenue-constraint being paid for in product headroom. Both are the company's commitments arriving at the moment those commitments become expensive.

For the Monday-morning discourse, the question is whether Cherny's concession stabilizes the community or exposes a larger pattern. The Fortune investigation — the April 14 piece that Fortune's technology desk pushed on the grounds that "lack of transparency accusations" had been accumulating for months — set up a news cycle the Opus 4.7 release did not end. [5] Cherny's Threads post, visible, informal, and specific, attempts to close the loop. The developer responses below it suggest the loop is reopened by each new benchmark that confirms token inflation at fixed cost. Arielldv on Threads put it cleanly to Cherny: "The advice for Max users hitting Claude Code limits is to use Sonnet instead of Opus and lower the effort level. So we're paying top dollar to... not use the top model? Then we should assume this is the new normal?" [1] Anthropic has not answered that question. Cherny has not either. The rate-limit increase addresses the symptom; the structural question about per-tier product consumption at fixed price remains open, and the mutiny that prompted the concession has kept asking it.

-- ANNA WEBER, Berlin