Nothing changed. Anthropic paused the Claude Agent SDK billing split on June 15, 2026, the day it was due to go live, so it is not in force. The paused plan would have pulled automated Claude usage (the Agent SDK, headless runs, GitHub Actions, and third-party agent apps) out of your subscription and onto a separate dollar credit billed at standard API rates. That move did not happen. Programmatic Claude usage still draws on your existing Pro, Max, Team, or Enterprise limits, exactly as before, and there is no new credit to claim. Anthropic says it is reworking the plan and will give advance notice before any revised version ships.
Short answer: announced, then paused before it went live
Anthropic told subscribers about the change in a note on May 13, 2026, then detailed it in its Help Center on May 14, 2026. The plan set a June 15, 2026 start. On June 15, before the new terms switched on, Anthropic confirmed in its Help Center and to subscribers that the move is off. Agent SDK, claude -p, and third-party app usage still count against your normal subscription pool. The company says it wants to better align the plan with how people actually use agents, and there is no credit to activate in the meantime.
Status as of June 16, 2026: nothing changed. Your subscription still pays for both your typing and your scripts. The proposed split is on hold, not in force.
What the paused plan would have moved out of your subscription
Four surfaces were slated to leave the subscription pool. The Claude Agent SDK, used for personal and programmatic projects. The claude -p command, the headless non-interactive mode that scripts and CI jobs call. Claude Code GitHub Actions, which run agentic work inside your repos. And third-party apps that authenticate through the Agent SDK. Team and Enterprise plans were to get per-seat allocations rather than one shared figure. Because the change is paused, none of it moved. If your workflows touch those four paths, they still bill against your plan today.
The common thread in the proposal was automation. Anything where a machine, not a person, issues the requests would have been reclassified. A nightly job that summarizes commits. A Slack bot wired to the SDK. A GitHub Action that reviews pull requests. A batch pipeline that tags support tickets. All of these ride under the flat subscription today, and they still do. The plan would have shifted them to a dollar balance that resets monthly, but that meter never switched on.
The per-tier credit math that was proposed: $20 Pro, $100 Max 5x, $200 Max 20x
The paused plan attached a monthly agent credit to each tier on top of the interactive subscription. Pro would get $20. Max 5x would get $100. Max 20x would get $200. Team and Enterprise seats carried per-user allocations in the same range. That credit was to be spent at standard API list rates, the same per-token pricing the API already charges, so the dollar figure was a real spending cap, not a token allowance. The proposal included no rollover: unspent credit would vanish at the end of the cycle. None of this is billing you now, because the change did not go live.
What would $20 have bought in practice? Not much agent work. At API rates, a few dollars covers a lot of short prompts but very little of the long-context, multi-turn, tool-heavy loops agents actually run. A single Claude Code session reviewing a large diff can read tens of thousands of input tokens, write thousands more, then loop. Schedule that across a team and a $20 Pro credit drains in days, not weeks. The Max 20x $200 credit bought more headroom, but it was still a meter. That math is the likely reason the proposal drew enough pushback to be pulled.
The proposed credit was a dollar cap priced at API rates, not a generous token bucket. It is not charging you now, but it signals the budget model a revised version may revive.
| Surface | Today (change paused) | If the proposed split returns |
|---|---|---|
| Interactive chat (app, terminal) | Subscription pool | Subscription pool, unchanged |
| Agent SDK / programmatic | Subscription pool | Separate credit, API rates |
| claude -p (headless) | Subscription pool | Separate credit, API rates |
| Code GitHub Actions | Subscription pool | Separate credit, API rates |
| Credit when exhausted | Not applicable | Requests stop, or API-rate overflow |
| Rollover of unused credit | Not applicable | None, resets monthly |
| Pro / Max 5x / Max 20x credit | Flat plan only | $20 / $100 / $200 monthly |
What is unaffected either way: human chat stays on your subscription
Interactive usage was never in scope, and it is unchanged. Claude.ai on web, desktop, and mobile draws from your normal subscription limits. Interactive Claude Code in the terminal, where a person types and reads replies in real time, stays on the subscription too. The line the proposal drew was about who is driving: a human at a keyboard on the flat plan, a script or bot on the metered credit. Since the credit never launched, both sides currently sit on your subscription, and your bill and limits look the same as before.
Why Anthropic floated this: flat rates strain under agent token burn
The proposal answered an economics problem that has been building since Claude Code shipped. A human in a chat window sends a request, reads the answer, thinks, and sends another. An agent does not pause. It loops, calls tools, re-reads context, and can fire dozens of model calls to finish one task, burning far more tokens per minute than any person typing. Flat-rate subscriptions were priced around human pacing. When agents run at machine pacing, a single seat can consume what the plan assumed a whole cohort of users would.
That gap is what the flat subscription has been quietly absorbing. While most subscribers use Claude like a human assistant, the heavy programmatic outliers average out. Once automation becomes normal, the average moves, and a flat fee struggles to cover compute it never priced in. Splitting the pools would restore the link between what a workload costs to run and what the customer pays. The pause suggests Anthropic still wants that link but is reworking how to draw it, with a price war against OpenAI and its broader pricing posture in the background.
A person reads between requests. An agent never stops to think. Flat-rate pricing assumed the pause, and agents removed it. That tension did not vanish when the change did.
What most coverage will not tell you: this is a delay, not a cancellation
Headlines read the pause as a customer win and stop there. The more useful read is narrower. Anthropic did not abandon the split. It pulled a specific set of figures and a specific start date, then said a revised version may follow with notice. The structural problem it tried to solve, agents burning machine-paced tokens against human-paced pricing, is untouched. So the practical stance is not relief. It is a window. The meter is off now, which is the cheapest possible time to find out which of your workflows would have tripped it.
What to do this week
Confirm your status first: the change is paused, you owe nothing extra, and no agent will stop for lack of credit. There is no credit to claim and no toggle to flip. The real move is to get ready, because Anthropic has said a revised version may follow. Audit where your Claude calls originate. If everything runs through the interactive app or human-driven terminal sessions, you were never in scope. If you have GitHub Actions, scheduled jobs, claude -p in scripts, or any third-party app on the Agent SDK, those are the workflows a future split would meter.
Then estimate the spend you would face if the split returns. For each automated workflow, multiply how often it runs by the rough input and output tokens per run, and price it at API rates to get a monthly dollar figure. Compare that total to the proposed tier credit: $20, $100, or $200. Land under it and a future change costs you nothing extra. Land over it and you have flagged a workflow worth trimming now, while the meter is off, so a relaunch does not surprise your budget.
Cut token burn at the source while you are in there. Trim oversized context windows. Stop re-sending whole files when a diff would do. Cache prompts that repeat, and route cheap subtasks to a smaller model. Agents waste tokens re-reading the same material every loop, and that waste is invisible under a flat plan. Under any metered credit, every redundant token becomes a line item. Teams that make their automation lean now will feel the least friction if a revised split arrives.
The durable shift: human chat and machine automation are drifting into two products
The lasting signal is not the dollar figures, which are on hold and may change. It is the boundary Anthropic tried to draw between human chat and machine automation as two priced products with two billing models. The pause shows the line is contested, not that it is gone. Interactive use stays a predictable subscription. Programmatic use is the part vendors keep trying to reprice as forecastable consumption. Expect more attempts, because the same agent economics pressure every vendor that once bundled automation under a flat seat. Planning agent spend as a metered line item is becoming part of building on these platforms.
Your subscription buys conversation. A metered credit, if it returns, buys computation. Budgeting for both is a sensible default even while the change is paused.
Lean agents start with what you do not re-send
Whether or not a token has a price today, stuffing the context window on every loop costs real compute. Much of an agent's burn is repetition: re-reading the same project notes, user preferences, and prior decisions on every run because it has nowhere durable to keep them. An external memory layer addresses that directly. MemX, an AI memory app from Neural Forge Technologies, stores facts and context once and lets an agent retrieve only what a task needs, instead of replaying the full history into the prompt each time.
On privacy, MemX is private by architecture: per-user isolation, encryption at rest, key management through Google Cloud KMS, and on-device handling where it applies. It will not make a heavy agent free, and it is not a billing workaround. The honest framing is narrow: if metered API-rate credits return, the cheapest token is the one you never resend, and a dedicated memory layer is one practical way to send fewer of them.
01Did the Claude Agent SDK billing change take effect on June 15, 2026?
No. Anthropic paused the change on June 15, 2026, the day it was due to start. Agent SDK, claude -p, GitHub Actions, and third-party app usage still draw from your existing subscription limits, and there is no new credit to claim.
02When was the change announced, and why was it paused?
Anthropic notified subscribers on May 13, 2026 and detailed it in its Help Center on May 14, 2026, for a June 15 start. It paused on June 15, saying it is reworking the plan to better align with actual usage, amid pricing pressure from a price war with OpenAI.
03What were the proposed agent credit amounts per plan?
As proposed, Pro would get $20 per month, Max 5x $100, and Max 20x $200, with Team and Enterprise seats in the same range. The credit was to be spent at standard API rates with no rollover. None of it is billing you now, because the change is paused.
04Does anything change for chatting with Claude in the app?
No. Interactive use on claude.ai web, desktop, and mobile, plus human-driven Claude Code in the terminal, was never in scope and stays on your subscription. The paused proposal only targeted programmatic surfaces.
05Should I still prepare for a separate agent credit?
It is reasonable. Anthropic said a revised version may follow with advance notice. Audit which workflows are automated, estimate their token spend at API rates, and trim repeated context now while no meter is running, so a future relaunch does not surprise your budget.
The change is paused, not cancelled. Set a reminder to recheck Anthropic's Help Center before your next billing cycle, and note which of your workflows are agent-driven so you can price them fast if a revised split is announced.
