Anthropic is moving programmatic Claude usage off your subscription pool onto a separate, dollar-metered credit pool. Interactive use is unchanged. Here's who's affected and what to do before June 15.
claude -p, Claude Code GitHub Actions, or a third-party agent, that usage leaves your normal subscription limit on 2026-06-15 and starts drawing from a fixed monthly credit billed at full API rates, with no rollover. If you only use Claude Code interactively in your terminal (and claude.ai / Cowork), nothing changes.
| Pool | What it covers | How it's billed |
|---|---|---|
| Interactive (unchanged) | claude.ai web/desktop/mobile, Claude Code used interactively in the terminal, Claude Cowork | Your normal subscription limits, exactly as before |
| Agent SDK credit (new) | Agent SDK, claude -p, Claude Code GitHub Actions, third-party agent apps | A fixed monthly dollar credit at full API list prices, no rollover |
| Plan | New Agent SDK credit / month |
|---|---|
| Pro ($20) | $20 |
| Max 5× | $100 |
| Max 20× | $200 |
Metered at full API list prices with no rollover. Because it's billed at API rates rather than the subscription's effective rate, heavy programmatic users can see the same workload cost noticeably more once it draws from this pool — which is why estimating your programmatic usage before June 15 matters.
claude -p "…" in scripts or cronclaude -p / CI / Agent SDK workload already costs more than your plan's credit at API rates, plan to reduce it or budget the overflow.If you're affected, the lever is spending fewer tokens per programmatic run so the new credit lasts. The biggest wins are usually prompt-cache hygiene, model selection per task, trimming context that's re-sent every turn, and catching cost-spike patterns (large tool outputs, hook stderr re-injection, duplicated context). A field reference of 13 Claude Code cost-spike patterns (free) covers the common ones with a defense for each.
No. Interactive terminal use keeps drawing from your normal subscription limits. Only programmatic usage (Agent SDK, claude -p, GitHub Actions, third-party agents) moves to the new credit pool.
They draw from a fixed monthly credit ($20 Pro / $100 Max 5× / $200 Max 20×) metered at full API list prices, no rollover. Estimate your current programmatic token spend at API rates to see whether you'll exceed it. If you do, you either reduce usage or enable usage-credit overflow (billed at API rates).
By default, programmatic requests past the credit are rejected. If you enable "usage credits," they instead bill at API rates so your automation keeps running. Choose based on whether budget or uptime matters more for that workload.
No action required for interactive use. It's worth claiming the credit anyway in case you start using agents later.
Not for interactive use. For programmatic use it can effectively raise cost, because that usage now bills at full API list prices from a capped credit rather than drawing from the subscription's effective rate. Heavy automation users feel it most.
Independent summary by an operator running Claude Code 800+ hours, maintainer of cc-safe-setup (free MIT hooks). Announced by Anthropic on 2026-05-14, effective 2026-06-15 — always confirm the exact terms against Anthropic's own claim email and docs, since plans can change. For a deep, field-tested guide to cutting Claude Code token cost (the lever for surviving the new credit pool), see the Token Book (Claude Code Token Optimization Guide, English). Not affiliated with Anthropic.