Claude's June 15 billing change — cancelled before it took effect
In brief
Anthropic planned to move programmatic usage (Agent SDK, `claude -p`, Code GitHub Actions, third-party agent apps) off subscription limits and onto a separate metered credit on June 15, 2026. On June 15, it cancelled the change. Nothing changes for now: those surfaces still draw from your Pro, Max, Team, and Enterprise limits exactly as before. Here's the full story, why it matters, and what to watch for next.
Contents
Update — June 15, 2026: this change was cancelled. Anthropic confirmed in its Help Center that the planned move of Agent SDK,
claude -p, and third-party app usage to a separate monthly credit is no longer happening. Nothing changes for now: those surfaces continue drawing from your Pro, Max, Team, and Enterprise subscription limits exactly as before. There is no credit to claim, and your subscription limits are unchanged. Anthropic says it is reworking the plan "to better support how users build with Claude subscriptions" and will give advance notice before any future change takes effect. The rest of this article explains what the proposed change was and why it matters — it's now history, not a deadline.
What was supposed to happen
On May 14, 2026, Anthropic announced that programmatic Claude usage would split off from subscription rate limits starting June 15, 2026. Under the proposal, programmatic usage would have moved to a separate, dollar-denominated monthly credit, metered at standard API list prices.
What would have counted as "programmatic" (moving to the new credit pool):
- The Claude Agent SDK running in your scripts and projects
claude -p— the headless / non-interactive mode of Claude Code- Claude Code GitHub Actions
- Third-party apps that authenticate using Agent SDK credentials (the path that lets editor integrations and tools run on your subscription)
What would have stayed the same:
- Interactive Claude Code in your terminal
- Claude web and desktop chat
The simple rule was: if a human is sitting there typing, unchanged; if code is calling Claude on its own, it spends from the credit pool.
The numbers that were proposed
Each plan would have received a fixed monthly credit, billed at full API list rates:
| Plan | Proposed monthly programmatic credit |
|---|---|
| Pro | $20 |
| Max 5x | $100 |
| Max 20x | $200 |
| Team Standard | $20 / seat |
| Team Premium | $100 / seat |
The detail that drew the most concern: the credit was per user with no rollover, metered at API list prices — and Enterprise Standard seats were slated to get $0 in new credits. For anyone running agents or CI against a subscription, $20 of Opus usage at list price is not many agent runs, so for heavy programmatic users it read as a large effective price increase.
Why it was proposed — and why the reversal matters
The original rationale was straightforward: a flat subscription fee with uncapped programmatic access meant some users ran heavy automated workloads — agents looping for hours, CI calling Claude on every commit — that cost far more in compute than the subscription brought in. Metered credit would have aligned price with cost.
The reversal matters for a practical reason beyond the refund-that-isn't: it's a reminder that subscription-based programmatic access is on notice. Anthropic didn't say "never" — it said "not like this, not yet." If your production setup depends on running agents cheaply against a Pro or Max subscription, that's a dependency with a question mark over it. The proposal getting pulled buys time; it doesn't remove the underlying economics that prompted it.
What to actually do now
- Don't claim anything. There is no credit and no email to act on. If you see a "claim your credits" message, it's stale.
- Know your real programmatic spend at API rates anyway. This was good advice before the change and it's good advice now: get one number — what would your current Agent SDK /
claude -p/ GitHub Actions usage cost at API list prices per month? Run/usageor pull the Usage & Cost API. If that number is large, you're exposed to whatever the reworked plan turns out to be. - Have an exit plan for heavy workloads. If you're well into "this would cost real money at API rates" territory, a proper API key with its own billing and rate limits is the stable foundation — independent of how subscription billing evolves.
- Watch for the advance notice. Anthropic committed to giving notice before any future change. If you own CI or production agents, that notice is the thing to catch — not a June 15 deadline that no longer exists.
Who this affects
If you're an Agent Operator running production agents off a subscription, or a developer with Claude wired into CI: nothing changes today, but treat your subscription-funded automation as a temporary arrangement and know your API-rate number. If you only ever use Claude by typing in the terminal or the web app: this never applied to you, and still doesn't.
Try this today
Run claude /usage or pull last month's programmatic usage from the Usage & Cost API, and write down one number: your monthly programmatic spend at API list prices. The June 15 change is gone, but that number is exactly what the next proposal will be priced against — so it's worth knowing before the advance notice lands.
Related reading
- When your AI model disappears — the broader lesson on not over-depending on one billing or model arrangement
- Claude Code, May 2026 updates — including the
/usagecost breakdown - The Rate Limits API — reading your limits and usage in code
Sources: Anthropic Help Center confirmation that the June 15, 2026 credit change is no longer happening; original change announced May 14, 2026. See coverage of the reversal.