What happened
Anthropic released Claude Opus 5.5 this week, with input tokens priced at $4 per million and output tokens at $20 per million, down 20% from $5 and $25. Anthropic reports a 40% cost reduction on typical workloads at default settings, reflecting cache pricing and token use as well as those rates. Tokens are the small chunks of text a model reads and writes; API pricing is quoted per million of them. A faster mode is also available at $8 per million input and $40 per million output, which Anthropic says runs up to 2.5 times faster.
Two things changed for Claude Code specifically, and both need action from you to matter.
First, five-hour session limits on Pro, Max, Team, and seat-based Enterprise plans went up 20% the day Opus 5.5 launched, according to Anthropic’s own Claude Devs account. Alongside that, Anthropic added a new kind of rate limit reset: one you save and trigger yourself, whenever you actually need it, instead of a blanket reset Anthropic applies to every account at once. To use it, go to Settings > Usage on Claude.ai or Claude Desktop and select “Reset for free.” Anthropic’s support documentation confirms the reset is not available in Claude Mobile or inside Claude Code’s terminal or IDE integrations, and that some resets carry expiration dates shown in your account’s Usage page. Once activated, it can’t be undone, and it doesn’t refund usage you’ve already spent or change your underlying plan.
Second, Claude Code’s cloud sessions moved out of research preview and are now available to everyone on Pro, Max, Team, and qualifying Enterprise plans. A cloud session runs your Claude Code work on Anthropic’s own servers instead of your laptop, so a task keeps running after you close the lid. Anthropic’s ClaudeDevs account announced a one-time launch credit for existing Pro and Max subscribers: $100 on Pro and $250 on Max. The announcement described cloud sessions using that credit before normal plan usage. The launch offer’s claim deadline was October 7. For GitHub-based sessions, connect the account and grant the required repository access. Current cloud-session documentation also describes uploading a local repository without GitHub in supported setups.
Why it matters
The saved reset requires activation, and the promotional cloud credit required a claim. The five-hour limit increase is separate: users did not need to activate a reset to receive that increase. A reset’s expiry, if it has one, appears in Usage settings; do not assume every reset has the same deadline as a credit promotion.
The rate limit reset also isn’t reachable from Claude Code itself, only from the Claude.ai or Desktop app’s Usage settings. If you live entirely inside a terminal or your editor’s Claude Code integration, you won’t see the option unless you go look for it somewhere else.
Who should care
Anyone on a paid Claude plan who regularly hits the five-hour session limit while working, and anyone curious about running Claude Code tasks that outlast a laptop session, such as a long refactor or a multi-step migration you’d normally have to babysit. Teams on Enterprise plans without premium or Chat + Claude Code seats should check with an admin, since cloud sessions require org-level access that isn’t universal across every Enterprise tier.
What builders should do next
Open Settings > Usage in Claude.ai or Claude Desktop and check whether a reset is available, which limit it restores, and any expiration date. Choose when to use it based on your current allowance and planned work; activation cannot be undone.
The October 7 launch-offer claim deadline has passed. Check any credit already claimed and how cloud sessions draw from your plan before starting a task. For a trial, choose a repository task with clear acceptance checks and review the result before merging or deploying it.
Updated October 13, 2026: input and output token rates fell 20%; Anthropic’s 40% figure describes typical workload costs. The limit increase is separate from activating a saved reset, and current cloud sessions can also upload supported local repositories without GitHub. The launch credit claim deadline was October 7.
End of article