What happened
Anthropic released Claude Opus 5.5 this week, cutting the model’s price by 40% on typical workloads compared to Opus 5: input tokens now cost $4 per million and output tokens $20 per million, down from $5 and $25. 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, running 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. To mark the change, Anthropic is giving existing Pro and Max subscribers a one-time credit, $100 on Pro and $250 on Max, that cloud sessions spend before falling back to your normal plan usage. You have to claim it by October 7, and it requires a connected GitHub account before you can start a session.
Why it matters
Both of these are opt-in. Anthropic isn’t crediting your account or resetting your limits automatically, and neither benefit rolls over if you forget about it. That’s a change from the pattern of prior Claude resets, which applied to every eligible account without a button to press. If you don’t check your Usage settings or claim the credit page, you get the price cut and nothing else this week.
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 today and check whether a reset is available on your account, along with its expiration date if one is shown. Save it for a task you know will run long, rather than triggering it the moment you see it, since it can’t be undone or reused once spent.
If you haven’t tried a Claude Code cloud session, claim the credit before October 7 and connect GitHub first, since a session can’t start without it. Use the credit on a real task you’d normally avoid starting right before closing your laptop, so you can judge whether the always-on session is actually useful for your workflow before the free credit runs out and it starts drawing from your regular plan usage.
End of article