Claude Opus 4.7 Launched: Why Anthropic Just Resolved the Drama Around Pro Limits
Three weeks of escalating drama, dozens of viral X threads, a flood of cancellation posts on r/ClaudeAI, and one near-meltdown for Anthropic's brand later, the company shipped Claude Opus 4.7 on April 11, 2026 - along with a quiet but enormous walk-back of the peak-hour usage throttle that had defined the worst stretch of consumer-product PR Anthropic has ever weathered. Here's what actually shipped, what changed for paying users, and the timeline of how it played out.
The Limits Saga - Three Weeks That Shook Anthropic
| Date | Event |
|---|---|
| March 27, 2026 | Anthropic rolls out a peak-hour session-drain adjustment on weekdays 1–7 PM UTC. Weekly limits unchanged but consumed faster during peak (see our deep-dive). Communicated only via in-app notice. |
| March 28–30 | Claude Pro and Max users start hitting weekly limits in days. Posts about "Claude is throttled" go viral on X, Hacker News, and Reddit. |
| April 1–7 | Anthropic publishes a help-center note clarifying the change but does not roll it back. Cancellations climb. Devs publicly switch to Cursor + GPT-5.4 / Codex. |
| April 8–10 | Several prominent AI infrastructure analysts publish write-ups suggesting the throttle is a sign of a capacity crisis at Anthropic. Stock-private sources speculate about urgent fundraising. |
| April 11, 2026 | Anthropic ships Opus 4.7 with materially better latency. The peak-hour drain is technically still on, but with a sharply narrower window and reduced drain multiplier - effectively unobservable for typical users. |
| April 14, 2026 | Google announces a $40B investment in Anthropic (covered in our analysis). The compute angle of the limits saga becomes obvious in retrospect. |
What's New in Claude Opus 4.7
The 4.7 release was technically a point bump, but the practical improvements were larger than the version number suggests:
- 1M token context now the default tier. The separate "long-context" SKU is gone. Every Opus 4.7 request supports up to 1M tokens at standard pricing - no special endpoint, no extra latency penalty.
- ~30% lower median latency than Opus 4.6 on long-context requests. Anthropic credits a re-architected attention pass; the timing also lines up with the start of the TPU rollout.
- Extended thinking is now controllable. A new
thinking_budget_tokensparameter caps how much internal reasoning Claude can do per request - a direct cost-control lever that didn't exist in 4.6. - Improved tool use reliability. Multi-step agentic sessions hit fewer dead-ends. The Claude Code team reports a measurable drop in retry-loop edge cases.
- Vision now matches text quality. Image-grounded reasoning was already strong; in 4.7 it's effectively at parity with pure text reasoning, which closes a long-standing gap with GPT-5.4.
- Better refusal calibration. Fewer false-positive refusals on benign coding/research prompts. This was a quiet but widely appreciated change.
Benchmarks vs. 4.6
| Benchmark | Opus 4.6 | Opus 4.7 | Delta |
|---|---|---|---|
| SWE-Bench Verified | 71.8% | 74.2% | +2.4 |
| GPQA Diamond | 83.6% | 85.1% | +1.5 |
| MATH-500 | 92.1% | 93.7% | +1.6 |
| MMLU-Pro | 78.9% | 80.4% | +1.5 |
| Long-context retrieval (256K–1M) | 91.0% | 96.4% | +5.4 |
The biggest jump is on long-context retrieval, which was a real weak point in 4.6 - the model would technically accept a 1M-token prompt but struggled to attend reliably to information past ~600K tokens. 4.7 closes that gap.
Pricing
| Model | Input ($/1M tokens) | Output ($/1M tokens) | Cached input ($/1M) |
|---|---|---|---|
| Claude Opus 4.6 | $15.00 | $75.00 | $1.50 |
| Claude Opus 4.7 | $15.00 | $75.00 | $1.50 |
| Claude Sonnet 4.6 | $3.00 | $15.00 | $0.30 |
| Claude Haiku 4.5 | $0.80 | $4.00 | $0.08 |
Pricing held flat. The capability uplift comes "for free" relative to 4.6. Use our price comparison tool to model your spend across the full Claude lineup.
What Changed for Pro and Max Users
For consumer-plan users, three concrete things changed on April 11:
- Default model. Pro and Max users now route to Opus 4.7 automatically. No setting change required.
- Effective allowance. The peak-hour drain multiplier dropped from ~2x to ~1.2x. Combined with the lower latency of 4.7 (which means you finish each task faster), most users report the practical experience now feels like the pre-March 27 baseline.
- Long-context in chat. Free 1M-token context applies to chat sessions, not just API calls. Drop a 500-page PDF into a Pro chat and it just works.
Should You Upgrade?
Migration from 4.6 to 4.7 is automatic on the API - the model ID is updated, but old claude-opus-4-6 requests still route correctly. Existing prompt patterns generally work without modification. The new thinking_budget_tokens parameter is opt-in.
For agentic coding workloads (Claude Code, custom agents), the latency improvement alone is worth the upgrade - 30% faster tool-use round-trips compounds over a long session. For chat workloads, the user experience is materially smoother but not transformative.
What This Says About Anthropic's State of Mind
The fact that Opus 4.7 shipped days before the public Google deal announcement is interesting. It suggests the engineering team had been racing to get a release out that could be paired with the financing news - a coordinated narrative reset. Whether that's good media strategy or simply good operational coincidence, the result is the same: by mid-April, the limits drama was effectively over and the conversation moved on.
For users who canceled in late March or early April: if you came back, the experience is now meaningfully better than what you left. For users still on the fence: the pricing/capability tradeoff vs. GPT-5.4 and Gemini 3.1 Pro is the cleanest it's been all year.
Frequently Asked Questions
Is the peak-hour throttle gone?
Technically still in place, but the multiplier was reduced enough that most users will not notice it. Anthropic has not officially "removed" it - they reduced its impact.
How is Opus 4.7 different from 4.6?
Faster (~30% lower latency), better long-context retrieval (96.4% vs 91% at 1M tokens), 1M context as default, controllable thinking budget, slightly higher reasoning benchmarks, better tool-use reliability.
Did the price change?
No. Same input/output/cache pricing as 4.6.
Should I update my code?
Old claude-opus-4-6 calls still work. To get 4.7 explicitly, use claude-opus-4-7. The new thinking_budget_tokens parameter is optional and only applies if you're using extended thinking.
What is thinking_budget_tokens?
A new request parameter that caps how many tokens Claude can spend on internal reasoning before producing the user-visible response. Useful for cost control and latency tuning on extended-thinking-enabled requests.
Is the limits drama really over?
For now. The underlying capacity issue was real, and the Google investment relieved it for the foreseeable future. If demand spikes again before the new TPU capacity is fully online, the throttle could tighten again - but that's a Q3/Q4 risk, not a near-term one.
What if I prefer the 4.6 behavior?
You can still pin to claude-opus-4-6 via the API. Anthropic has not deprecated it - 4.6 will remain available for at least 12 months from the 4.7 release date. Pro/Max chat users do not have a model-pin option and route to 4.7 automatically.
For the broader investment context behind these limits changes, see our analysis of the Google–Anthropic deal. Track Claude pricing and capabilities on our models page, and use our Token Calculator to estimate API costs for your specific workload.