Claude Cloud Session Credit vs Usage Credits vs Limit Reset

Updated October 8, 2026. The cloud session credit could only be claimed until October 7, 2026, so that window has closed. On the same day, Anthropic added monthly API credits to Max and Team plans, a fourth "credit" that pays for something else again.

The four Claude credits pay for different things. The cloud session credit was a one-time promotional balance from Anthropic ($100 on Pro, $250 on Max) that only works inside Claude Code cloud sessions. If you claimed it, you keep spending it until it runs out. Usage credits are your own money: prepaid funds, billed at standard API rates, that keep Claude and Claude Code running after your plan's included usage runs out. A limit reset costs nothing and refills either your five-hour session limit or your weekly limit once, account-wide. Monthly API credits on Max and Team pay for the Claude API and the Agent SDK through a linked Console organization, and they don't extend your plan limits at all.

If you're blocked by a limit, spend the free value first. Use any cloud credit balance you already claimed, check whether you hold an unused reset in Settings > Usage, and only then turn on usage credits with a monthly cap. A reset doesn't refund usage credits you've already been billed for, so using it after paying is money you can't get back. Monthly API credits won't unblock you: they can't pay for interactive Claude Code or for usage beyond your plan's limits.

The four Claude credits side by side

Sources: ClaudeDevs announcement, Manage usage credits for paid Claude plans, What is a limit reset?, Monthly API credits for Max and Team plans, as of October 8, 2026.

Only one of the four reaches the Claude Console or API: the Max and Team monthly API credits, and that's all they do. The other three stay inside your subscription. A subscription and the API are billed separately, and cloud sessions need a claude.ai sign-in, not an API key.

This chart predates the October 8, 2026 update: its API row doesn't show the Max and Team monthly API credits. The table above is current.

Cloud session credit: claims closed October 7, balances still work

Cloud sessions are Claude Code sessions that run on Anthropic-managed machines, so they keep working after you close your laptop. They left research preview on September 23, 2026, and are available on Pro, Max, and Team, and to Enterprise users with premium or Chat + Claude Code seats (Claude Code on the web docs).

To mark the launch, Anthropic's developer account announced a credit for existing subscribers: "$100 on Pro, $250 on Max." The thread spelled out the rules (post 2, post 3):

• "The credit is separate from your usage limits, and it applies automatically once you start a cloud session."
• "If you hit a limit locally, keep going in the cloud until your credit runs out."
• "One credit per account, for cloud sessions only."
• Claiming worked through the link in the post or with /claim-credit in the CLI, and the post said "Claim by Oct 7. Terms apply."

That deadline has passed. Anthropic hasn't announced a second claim window, so the claim link and /claim-credit are history rather than a step you can still take.

If you claimed the cloud credit before October 7

Your balance keeps applying automatically whenever you start a cloud session, until it runs out. You still need GitHub connected to start a session. Anthropic hasn't published an expiry for claimed balances: the announcement gave only the claim deadline, there's no help-center article on the credit, and the full terms sit behind the claim page. If a long cloud job depends on that balance, run it sooner rather than later.

If you didn't claim it, you lost a bonus, not a feature. Cloud sessions still run on your plan's included limits, as the next section explains.

Cloud sessions didn't become a paid feature

The credit announcement can read as if cloud sessions now cost extra. They don't. The docs say cloud sessions "share rate limits with all other Claude and Claude Code usage within your account" and "there is no separate compute charge for the cloud VM." So a cloud task draws on the same five-hour and weekly limits as a local one. Several tasks in parallel drain those limits proportionally faster. The credit was extra value on top of your plan, not a new price for something you had.

What the announcement left open

As of October 8, 2026, three questions about the credit have no public answer:

• Expiry after you claimed. Only the claim deadline was published.
• Team and Enterprise eligibility. The posts named only Pro and Max.
• Draw order while you still have plan allowance. It's not stated whether a cloud session spends your included usage or the credit first.

The last one matters only when you aren't blocked. Once a local limit stops you, your included usage is used up, and the credit is what keeps the cloud session going. To see what happens with allowance left, note your session and weekly bars in Settings > Usage, run a short cloud task, and check whether the bars moved.

Cloud sessions also have entry requirements. They don't work when Claude Code signs in with an API key or runs through Amazon Bedrock, Google Cloud, or Microsoft Foundry, and organizations with Zero Data Retention can't use them. Cloning and pull requests need GitHub. A GitLab or Bitbucket repo can be sent as a local bundle (CCR_FORCE_BUNDLE=1), but the session can't push results back to it.

Usage credits: your own money at API rates

Usage credits are for individual Pro, Max 5x, and Max 20x plans. With them turned on, hitting a limit no longer stops you. After a notice and a confirmation, the rest of your work is billed at standard API rates and shows up as a separate charge from your subscription.

Setup lives in Settings > Usage on the web. If you subscribed through the iOS or Android app, you still have to enable them on the web:

1. Click Enable in the Usage credits section and add a payment method.
2. Set a monthly cap with Adjust limit. "Set to unlimited" removes it.
3. Prepay with Add funds. Auto-reload can top up your balance when it drops below a threshold you choose.

A daily redemption limit of $2,000 applies. You can switch usage credits off at any time, which puts you back on your plan's included usage only. They don't change when your limits reset: the session limit still resets every five hours.

On Pro, usage credits can matter before you hit any limit. Fable 5 and Fable 5.1 aren't included in Pro's usage limits, so they run on usage credits from the first request. On Max, Fable models can use up to 50% of your weekly limit at no extra cost, and past that you continue on usage credits or switch models (Claude Fable models on your plan).

In Claude Code on a subscription login, /usage-credits opens those settings and shows your balance, monthly spend, and cap. /usage adds a usage-credits row while they're on. When a limit blocks you, /rate-limit-options lists your choices: wait and continue automatically after the reset (Claude Code v2.1.234 or later), add usage credits, or upgrade (Claude Code costs docs). None of these commands work with API key authentication.

One cost detail is easy to miss. Claude Code keeps its prompt cache for an hour on a subscription, but the cache lifetime "drops to five minutes once you're drawing on usage credits." After a coffee break, your next message reprocesses the full context, and you pay API rates for that. For the math on when credits cost more than moving up a plan, see Claude Extra Usage Cost: When Credits Get Expensive and When Max Is Cheaper.

On expiry, the help article says usage credits don't expire "in most cases." The named exception is Japan, where credits bought from September 10, 2026 expire six months after purchase, with an email seven days before.

Limit reset: one free refill of one limit

A limit reset is a benefit Anthropic hands out "occasionally" to eligible plans. The most recent one came with the Opus 5.5 launch on September 22, 2026, described as a reset "which you can now save and use whenever you choose" (Anthropic). Not every account holds one.

Each reset card targets one limit. Depending on the card, either your five-hour session limit or your weekly limit goes back to full immediately. Your weekly limit still resets on its usual day and time afterward. You don't need to be blocked to use it, but it can't be undone.

To use it, go to Settings > Usage on the web or in Claude Desktop, click Reset for free in the Resets section, and confirm. The same button appears on the message you see when you hit a limit. It isn't available on Claude Mobile or inside Claude Code in the terminal or an IDE. Because limits are shared across your account, a reset you trigger in the browser refills Claude Code too. Claude Code has no command for it.

Two rules decide timing. First, a reset "doesn't refund extra usage you've already been billed for or change your usage credit balance." Second, an unused reset disappears if you downgrade or cancel. Claude Opus 5.5 Pricing and Limit Reset: What Each One Changes covers what the Opus 5.5 reset restores in more detail.

Monthly API credits on Max and Team: API only, not plan limits

Anthropic added these on October 7, 2026, and they're the credit most easily mixed up with the other three. They're the only one that reaches the Claude API, and the only one that does nothing for a Claude or Claude Code limit. The Monthly API credits for Max and Team plans help article sets the rules:

• Amounts. Max 5x gets $100 and Max 20x gets $200 each billing cycle. Team gets $20 per Standard seat and $100 per Premium seat, pooled into one balance capped at $500 a month. A team with three Standard and two Premium seats gets 3 × $20 + 2 × $100 = $260.
• Who can't get them. Free, Pro, and Enterprise plans aren't eligible.
• How to claim. After seven days on an eligible plan, open claude.ai in a web browser and go to Settings > Billing (Max) or Organization settings > Billing (Team Owner or Primary Owner), then choose Link organization in the API credits section. You can link only one Console organization and can't switch it yourself. No payment method is needed. The rollout takes a few days, so the option may not show yet.
• What they pay for. Any available Claude model on the Claude Platform: the Messages API, the Message Batches API, the Playground, Claude Managed Agents, and the Claude Agent SDK. They're spent before any credits you bought for that organization.
• What they don't pay for. Interactive Claude Code in the terminal, IDE, desktop app, or web; usage beyond your plan's limits in Claude, Claude Code, or Claude Cowork; and Claude on Amazon Bedrock, Google Cloud Vertex AI, or Microsoft Foundry.
• claude -p and the Agent SDK. They're covered only when you run them with an API key from the linked organization. Signed in with your Claude plan, they still draw from your plan limits. Runs started by the Claude Code GitHub Action, an IDE extension, or the Claude desktop app count as Claude Code usage and aren't covered, even with -p.
• Timing. The credits refresh each billing cycle and don't roll over. If they run out and the organization has no purchased credits, API requests stop until the next month's credits arrive. Nothing is charged to your Claude plan.

They're also separate from the "Agent SDK credits" mentioned in June; the help article says that credit "isn't available." For how this fits with every plan's limits, see Claude Usage Limits by Plan: What 5x and 20x Actually Multiply. If you're still deciding whether a job belongs in your own code or in Claude Code, Claude API vs Claude Code: Which One to Use and How You Pay covers the split.

Which one to use first when a Claude limit hits

The rule behind every row below: free value first, paid value last, and the reset before any paid usage it could have replaced.

Two cases deserve a second look. A five-hour block ends on its own within hours, so a session-type reset spent on it is worth it only if the wait costs you more than the reset does. A weekly block can last days, and that's where a weekly reset saves the most usage-credit spend. And the announcement says "if you hit a limit locally, keep going in the cloud" without naming which limit, so a claimed balance isn't limited to the five-hour case.

If you're weighing the whole plan rather than one week, Claude Pro vs Max in 2026: Pricing, Claude Code Limits, and When Max Is Worth It compares the included limits.

Before you turn on usage credits

Run through this in Settings > Usage before adding funds:

1. Resets section. Is there an unused reset? Note whether it's a session or weekly reset and when it expires.
2. Cloud credit. Did you claim it before October 7, 2026, and is there balance left? Is the blocked work in a GitHub repo you could open in a cloud session?
3. Reset time. When does the limit that stopped you come back? If it's hours away, waiting may be enough.
4. Monthly cap. Set one with Adjust limit instead of "Set to unlimited," and decide whether auto-reload should be on at all.
5. Model and breaks. Anthropic suggests Sonnet or Haiku for most tasks, since they cost less per token than Opus. Remember the five-minute cache while you're on credits.
6. Dashboard split. The usage dashboard shows included usage and usage-credit spend separately. If credit spend appears while your plan bars still show room, screenshot it before contacting support.
7. Monthly API credits. On Max or Team, leave them out of this decision. They can't pay for interactive Claude Code or for usage past your plan limits.

If you're on Team or use an API key

Team and seat-based Enterprise. Cloud sessions are available to you and share your account's limits. The cloud credit posts named only Pro and Max, and the claim window has closed either way. Usage credits on these plans are managed by your admin under a separate help article, and /usage-credits may send your admin a request instead of opening settings. If your seat got a reset, it appears under Resets in Settings > Usage. Team plans also get monthly API credits, which the Owner or Primary Owner claims by linking one Console organization; Enterprise plans don't. On standard Team seats, Fable models run on usage credits, while premium seats can use up to half the weekly limit on them.

API key, Bedrock, Google Cloud, or Foundry. The cloud credit, usage credits, and limit resets don't apply to you. Cloud sessions and /usage-credits need a claude.ai sign-in, and a subscription reset doesn't add API credits or reset API rate limits. The one link between a plan and the API is the Max and Team monthly API credits: a key from your linked Console organization spends them on claude -p and Agent SDK runs, but not on Bedrock, Google Cloud, or Foundry, and the help article lists interactive Claude Code as not covered. To check which billing route your Claude Code actually uses, see Claude Code API Billing vs Subscription: API Key, Credits, or Pro/Max?

FAQ

Can I still claim the Claude cloud session credit?

No. Claims closed on October 7, 2026, and Anthropic hasn't announced another window. If you claimed it in time, the balance still applies automatically in cloud sessions until it runs out.

Do cloud sessions use my usage credits now?

Not by default. Cloud sessions share your plan's included limits and have no separate compute charge. A claimed cloud credit applies automatically when you start one. Usage credits only come into play after your included usage runs out and only if you've turned them on, the same as for local work.

Does the cloud session credit expire?

The claim deadline was October 7, 2026. For balances claimed before then, Anthropic hasn't published an expiry, and there's no help-center article on the credit. Treat it as a balance to use rather than one to save.

Do Max monthly API credits count toward my Claude usage limits?

No. They're "separate from your plan limits" and don't change your limits in Claude, Claude Code, or Claude Cowork. They pay for API usage in the Console organization you link, and unused credits expire at the end of each billing cycle.

Can I use a limit reset from Claude Code?

Not from the terminal or IDE. Use Settings > Usage in a browser or Claude Desktop. The refill is account-wide, so Claude Code picks it up right away.

Do Claude usage credits expire?

In most places, no. In certain jurisdictions such as Japan, usage credits bought from September 10, 2026 expire six months after purchase. You get an email seven days before, and expiration dates show on the Usage page in Settings.

How often do usage credits reset?

They don't. Usage credits are a prepaid balance that you top up, not an allowance that refills. What resets is your plan's included usage: the session limit every five hours and the weekly limit on its usual schedule.