QWE AI Academy The #1 mistake people make with Claude Opus 5.5 on Max right now: they treat it like Opus 5. They paste old “think hard” system prompts, slam effort to max on every turn, and burn a five-hour quota on loops that never needed that depth.
Flip it. Opus 5.5 already thinks on every reply. Your job is to define “done,” pick a sane effort level, and let Max’s higher limits run long agent jobs – not babysit verbosity.
What just dropped (quick context)
September 22, 2026: Anthropic shipped Claude Opus 5.5, model ID claude-opus-5-5, first model in the Claude 5.5 family. Official line from the Anthropic announcement – Fable 5.1-level work on most tasks, roughly 40% lower cost than Opus 5 on typical loads, output more than 30% faster.
API list prices as of that launch: $4 / $20 per million input / output tokens (20% under Opus 5), cache reads $0.20 (60% cut), 5-minute cache writes $5. Fast mode is $8 / $40 for up to about 2.5× speed. Context window 1M tokens; max sync output 128K. Knowledge cutoff June 2026 on the model card – treat web-fresh events as out of band unless you ground them yourself.
Opus 5.5 is on Claude apps for Pro and Max (and paid team tiers Anthropic lists at launch), plus the API. Five-hour usage limits on paid plans were raised the same day. Pricing and caps can move; check the live model overview before you budget a quarter.
Hands-on: Claude Opus 5.5 on Max in 15 minutes
Max is the all-day pool: about 5× Pro usage near $100/mo or 20× near $200/mo on US web pricing (Help Center; regional pages may show local currency). Sessions reset every five hours. Weekly caps still span chat and Claude Code.
1. Select the model and effort
- Open Claude (web/desktop) or Claude Code.
- Pick Opus 5.5 in the model picker (or
/modelin Claude Code). - Set effort to medium for daily coding and analysis. That is the API default now – not high like older Opus.
- Bump to high or xhigh only for multi-file refactors, hard debugging, or long agent jobs. Keep max for rare research-grade passes.
Thinking is always on. You cannot turn it off. On the API, thinking: {"type": "disabled"} or a manual budget_tokens value returns 400 invalid_request_error – depth is effort-only per the official what’s-new.
2. Hand over one complete task
Don’t drip instructions. One message with a finish line fits how this model runs.
Audit src/payments for the old Stripe client.
Done means: every call uses the new client, old helpers are deleted,
unit tests pass, and you list any endpoint you skipped with why.
Stop and ask only if a test fails for a reason you can't fix in-repo.
Do not expand scope to billing UI or docs.Strip “think step by step” / “be thorough” lines from CLAUDE.md and custom skills. Early users say old Opus 5 scaffolding confuses 5.5 and burns tokens.
Pro tip: On Max 20×, start a long Claude Code job before a meeting. Hard “done,” stop rule for destructive actions, read the summary when you’re back. Early tester write-ups describe multi-hour unattended runs this way.
3. Price-check before you scale
| Meter | Opus 5.5 (launch) | Opus 5 | |
|---|---|---|---|
| Input / MTok | $4 | $5 | |
| Output / MTok | $20 | $25 | |
| Cache read / MTok | $0.20 | $0.50 | |
| Fast mode in/out | $8 / $40 | n/a (prior gen differed) |
Cache reads dominate agent and coding bills. Prompt caching plus medium effort is how Max subscribers stretch a five-hour window. Fast mode doubles token rates – grab it when latency beats spend.
Common pitfalls that eat Max quota
- Max effort by default. Post-launch threads (r/ClaudeAI and similar) say max often overthinks and loops. Artificial Analysis put roughly $1.34 per Intelligence Index task at medium vs about $5.98 at max – same model family, very different burn.
- Forced tools on the API.
tool_choiceset toanyor a named tool → 400. Useautoand name the preferred tool in the prompt. - Silent medium default after migration. Swap only the model ID and results can look “weaker” than Opus 5-at-high until effort is set on purpose.
- Legacy skills. Text written to fix Opus 5 verbosity can shove 5.5 into odd over-corrections. Cut or rewrite it.
That’s the messy part of a hot launch: the model got simpler to talk to, but your old scaffolding didn’t.
Intelligence and performance: what the numbers actually mean
Numbers first. Anthropic’s launch table (max/xhigh effort, production safeguards on) lists Terminal-Bench 4.0 at 66.4%, FrontierCode at 54.4%, CursorBench at 57.8%, GDPval-AA v2.1 at 1846 Elo – strong on agentic coding and knowledge work.
Artificial Analysis had it at 58 on the Intelligence Index at max effort – top of 212 models at launch time – with medium still near ~51 on a much lower cost-per-task. Leaderboards move; those figures are launch snapshots.
What you feel day-to-day on Max: fewer turns to green tests. One internal-style story in the announcement: a 200k-line audit/fix in under three hours versus Opus 5 taking 20+ hours and 2.5× tokens. Your repo will disagree in places. Time it.
When NOT to use Opus 5.5
Skip it for bulk classification, short rewrites, or high-volume chat – Sonnet is cheaper and fast enough.
Expect friction on life-sciences and some cyber topics. Fable-class safeguards refuse more prompts; org verification programs exist, but individuals on Max still hit walls. Community reports line up with the stricter posture in Anthropic’s launch materials and system-card framing.
If your loop needs a forced tool call every turn with no prompt steering, redesign the loop or pick another path. Creative taste-testing with no shippable artifact? Sample Opus 5.5 against Fable before you lock Max spend.
FAQ
Is Claude Opus 5.5 available on the Max plan?
Yes. Opus sits on Pro and Max. Max is a bigger usage pool (5× or 20× Pro per five-hour window), higher output headroom, and priority – not a separate model SKU. Details: Max plan Help Center.
Should I always run max effort for “best” intelligence?
No. Max tops some benches and the AA Index, and it also melts output tokens. For a Max coding day, start medium. Escalate only when medium stalls on a concrete failure – failing tests, wrong architecture – not because the ticket “feels important.”
How does price compare if I leave Max and go pure API?
You’re comparing a shared subscription pool to a meter. Pure API on Opus 5.5 (launch rates): $4/$20 per MTok plus $0.20 cache reads. A heavy uncached agent weekend can blow past a Max invoice; cache-heavy iterative coding often lands cheaper on API once you log tokens. Pattern a lot of power users settle into: Max for interactive flow, API credits for overflow. Open Settings → Usage before you swear one path always wins.
Open Claude on Max, switch to Opus 5.5 at medium effort, paste one real backlog ticket with a one-line “done means,” and time how many turns you need versus last week on Opus 5. That single A/B beats another benchmark screenshot.