Verified against Anthropic documentation & release notes on · Updated
Claude Opus 5.5 usage limits: how quota, effort, and resets work
Claude Opus 5.5 usage on paid plans counts toward a 5-hour session limit and a weekly plan limit. Anthropic increased five-hour limits when Opus 5.5 launched, but publishes no universal message count or percentage increase. Opus 5.5 uses always-on adaptive thinking with a medium model default, and higher effort uses more tokens.
When you reach your 5-hour session limit, prompts pause until the stated reset time. When you hit the published weekly plan limit, switching from Opus to another model does not bypass it because the standard weekly limit applies across all models. Subscribers can monitor both limits using /usage in Claude Code or via Settings › Usage on the web, and continue past limits using optional Usage Credits.
Anthropic currently documents a five-hour session limit plus a weekly limit across all models. Check Settings › Usage for the exact meters and reset times assigned to your account.
Opus 5.5's documented model default is medium. Anthropic says lower effort uses fewer tokens and stretches usage further; Claude Code defaults can vary by plan or configuration.
Anthropic increased five-hour usage limits for Pro, Max, Team, and seat-based Enterprise plans at launch. It did not publish a universal percentage increase.
Logged-in Claude Code sessions share your web quota. Check live usage with /usage, tune reasoning with /effort, and compact history with /compact.
How Claude Opus 5.5 usage limits work: session vs. weekly
Using Opus 5.5 on a paid Claude plan draws against your session and weekly plan limits. Understanding which limit you are hitting determines how long you wait and what can actually restore access:
The rolling 5-hour session limit
The 5-hour limit regulates session usage. Anthropic documents that session-based usage resets every five hours, and Claude shows the specific reset time when you approach or reach the limit (for example, 5-hour limit reached - resets 3:15 PM).
For full reset timing and session window mechanics, read our 5-hour limit guide.
The weekly plan limit
Anthropic's current Pro, Max, and Team documentation says the weekly plan limit applies across all models and resets at a fixed day and time assigned to your account. Anthropic can also apply additional model- or feature-specific limits at its discretion, so use Settings › Usage for the exact meters on your account.
If the all-model weekly limit is exhausted, switching from Opus to Sonnet or Haiku does not bypass it. Learn more in our weekly limit guide or see how Claude Sonnet 5.5 limits draw from the general weekly pool.
Opus 5.5 limit comparison by subscription plan
| Plan | Price | 5-Hour Session Quota | Weekly Limit Tracking | Over-Limit Continuation |
|---|---|---|---|---|
Claude FreeFree Tier | $0 | Not available | N/A | Upgrade required |
Claude ProIndividual | $20/mo | Baseline 5-hour session allowance | Weekly limit across all models | Pauses until reset; optional Usage Credits |
Claude Max 5×Power Tier | $100/mo | 5× Pro 5-hour session capacity | Weekly limit across all models | Pauses until reset; optional Usage Credits |
Claude Max 20×Maximum Tier | $200/mo | 20× Pro 5-hour session capacity | Weekly limit across all models | Pauses until reset; optional Usage Credits |
Claude Team (Standard)Team Standard | $25/seat/mo | 1.25× Pro session capacity (per member) | Weekly limit across all models | Pauses until reset; org-managed Usage Credits |
Claude Team (Premium)Team Premium | $125/seat/mo | 6.25× Pro session capacity (per member) | Weekly limit across all models | Pauses until reset; org-managed Usage Credits |
Claude Enterprise (Usage-Based)Enterprise | Custom | No session cap (metered consumption) | No weekly allowance cap | Direct API billing governed by admin spend limits |
For full cross-plan comparisons including non-Opus models, consult our comprehensive Claude usage limits reference table.
What changed when Opus 5.5 launched
Released on September 22, 2026, Claude Opus 5.5 introduced direct architectural and billing changes that altered how subscription quotas deplete:
Opus 5.5 lowered standard API token prices to $4 per million input tokens and $20 per million output tokens, with cache reads at $0.20 per million tokens. Separately, Anthropic announced higher five-hour usage limits for Pro, Max, Team, and seat-based Enterprise plans, but did not publish a universal percentage increase.
Anthropic documents medium as the Opus 5.5 model default. Higher effort uses more tokens and reaches usage limits faster. In Claude Code, the effective default can vary by plan or configuration, so check the session before assuming it is medium.
Anthropic occasionally gives eligible accounts a saveable limit reset. The reset shown on your account can restore either the five-hour session limit or the weekly usage limit to full, and any expiry is shown in Settings › Usage. It is used from Claude on the web or Desktop, not directly from Claude Code.
Opus 5.5 supports up to 1,000,000 input tokens and 128,000 max output tokens. While massive context windows accommodate large repositories, cumulative re-processing on subsequent prompt turns burns allowance at an accelerated pace.
Reasoning effort levels: the primary quota lever
Because adaptive thinking is always active on Opus 5.5, the effort setting is one of the clearest controls you have over usage. Anthropic says higher effort uses more tokens and makes you reach usage limits faster, while lower effort stretches usage further.
Opus 5.5 in Claude Code vs. web chat
Opus 5.5 usage across Claude and Claude Code counts toward the same plan limits. Anthropic notes that Claude Code sessions can be significantly more token-intensive than chat, especially on long agentic tasks:
Web & Desktop Chat Behavior
- •Context consists of user messages and model replies.
- •Tool use varies by task, but ordinary chat often involves fewer autonomous tool loops than an agentic coding session.
- •Long conversations, attachments, tools, and higher effort can all increase usage even in chat.
Claude Code Terminal Behavior
- •Agentic coding can add repository files, directory listings, command output, and tool results to context.
- •Agent loops execute multi-step tools automatically, repeating context on every turn.
- •Background subagents run parallel model calls that rapidly multiply token consumption.
Best practices to prevent rapid Opus 5.5 quota exhaustion in Claude Code:
- 1.Run
/usagefrequently: Displays your active 5-hour session progress bar, 7-day weekly plan progress bar, and exact reset time. Learn more in our Claude Code usage guide. - 2.Compact before long turns: Run
/compactto compress conversational context once a task milestone is reached. - 3.Clear context between features: Use
/clearto wipe past history when switching to an unrelated bug or feature. - 4.Trim CLAUDE.md: Ensure project instruction files contain essential architecture guidelines rather than massive full-file dumps.
- 5.Consider API key auth for separately billed workloads: Claude Code usage authenticated with an API key does not consume your Claude subscription allowance. It is billed to the API account and remains subject to that account's API rate limits and pricing.
The 1M context window: practical usage realities
Opus 5.5 supports up to 1,000,000 tokens in a single context window. While this allows loading entire documentation sets or large codebases into a single session, the cumulative token mechanics of Claude subscriptions make running deep 1M conversations risky on included plans.
Why long context affects usage: Anthropic lists current conversation length as one factor that affects plan usage. Opus 5.5 supports a 1M-token context window on paid Claude plans, but filling that window does not make the usage limit disappear.
Anthropic uses caching to reduce the cost of reused content and automatically manages long conversations by summarizing earlier messages near the context limit. Even so, Anthropic says longer conversations and context management consume more of your usage limit, so starting a fresh conversation can help when a long thread is exhausting usage quickly.
To maintain high throughput on Claude Pro or Max, treat the 1M window as a tool for targeted queries rather than an ongoing dumping ground for your entire workspace.
How to check your Opus 5.5 usage
You can check remaining Opus 5.5 usage and reset timing across three primary surfaces:
1. Claude Web & Desktop Apps (Settings › Usage)
Navigate to your profile icon, select Settings, and click Usage. Paid plans show progress toward the current five-hour session limit and weekly limits, plus reset timing. Anthropic's current documentation describes the standard weekly limit as applying across all models; any additional model-specific meter shown here is account-specific.
2. Claude Code Terminal (/usage command)
Type /usage in any active terminal session. Claude Code outputs your rolling 5-hour session progress meter, 7-day weekly plan progress meter, reset timestamps, and model token breakdowns.
3. Terminal Statusline & Menu Bar
For real-time visibility while editing code, you can configure a Claude Code statusline or install our free, open-source local Claude usage tracker that displays your remaining session and weekly allowances in your macOS menu bar or CLI.
What happens when you hit an Opus 5.5 limit
When your account reaches an Opus limit, your next steps depend on which constraint was triggered:
Prompts pause until the rolling 5-hour reset time shown in the interface. When that moment arrives, your full session capacity restores automatically without logging out or restarting.
The published weekly limit applies across all models, so switching from Opus 5.5 to Sonnet or Haiku does not bypass an exhausted all-model weekly limit. Your next reset day and time are shown in Settings › Usage.
If you have optional Usage Credits enabled in Settings › Usage, Claude will continue processing Opus 5.5 requests without interruption when your included allowance is exhausted. Continuation is billed on actual token consumption at standard API rates ($4 per million input tokens, $20 per million output tokens).
Learn how to purchase discounted bundles and set spend caps in our Claude usage credits guide. If you are currently locked out, see our limit reached checklist.
Frequently asked questions about Opus 5.5 usage
Does Claude Opus 5.5 have a separate usage limit from other models?
Not as a universal published allowance. Anthropic's current help pages document a five-hour session limit plus a weekly limit that applies across all models on Pro, Max, and Team plans. Anthropic may also apply model- or feature-specific limits at its discretion, so Settings › Usage is the source of truth for any additional meter shown on your account.
How many messages or prompts do you get with Opus 5.5?
Anthropic does not publish a universal fixed message quota or token allowance for Opus 5.5. Practical capacity varies with conversation length, attachments, tools, model choice, and effort level. Anthropic increased five-hour usage limits when Opus 5.5 launched, but it did not publish a universal percentage increase or message count.
Is Claude Opus 5.5 available on the free Claude plan?
No. Claude Opus 5.5 is not available on the Claude Free tier. Accessing Opus 5.5 requires an active paid subscription (Claude Pro, Max 5×, Max 20×, Team, or Enterprise) or pay-as-you-go API Console access.
How does the effort level affect Opus 5.5 usage consumption?
Opus 5.5 uses always-on adaptive thinking and its model default is 'medium' effort. Anthropic says higher effort uses more tokens and makes you reach usage limits faster, while low and medium stretch usage further. Claude Code defaults can vary by plan or configuration, so check /effort in the session you are actually using.
Does Claude Code share the same Opus 5.5 limit as web chat?
Yes. Claude's help center says usage across claude.ai, Claude Desktop, and Claude Code counts toward the same plan usage limits. If you use Claude Code with an API key instead of your subscription login, that usage is billed separately to the API account and does not consume the subscription allowance.
What happens when you hit an Opus 5.5 usage limit?
If you hit the five-hour session limit, you normally wait for the reset time shown in Claude or continue with Usage Credits if enabled. The published weekly limit applies across all models, so switching from Opus to Sonnet or Haiku does not bypass an exhausted all-model weekly limit. Eligible accounts may also receive a limit reset that restores either the five-hour or weekly limit, depending on the offer shown in Settings › Usage.