Anthropic Splits Claude Subscriptions: What Changes for Indie Hackers on June 15

Yesterday, Anthropic announced a change that affects every developer using Claude Code for automation, CI pipelines, or third-party agent tools. Starting June 15, 2026, programmatic usage of Claude via subscription plans moves to a separate monthly credit pool.

The change comes after months of friction: Anthropic banned third-party agents from subscriptions in April, briefly tested removing Claude Code from the Pro plan, and now has landed on a new model. This post explains exactly what changes, who is affected, and what to do before June 15.

What Did Anthropic Actually Announce?

On May 13, via the official @ClaudeDevs account, Anthropic announced that Agent SDK and claude -p usage will draw from a new dedicated credit starting June 15, separate from your subscription's interactive usage limits.

The specific things moving to the new credit pool:

• Claude Agent SDK usage
• The claude -p command
• Claude Code GitHub Actions
• Third-party apps built on the Agent SDK (OpenClaw, Conductor, Zed, Jean)

The specific things staying on your subscription's existing limits:

• Interactive Claude Code in your terminal or IDE
• Claude chat on web, desktop, and mobile
• Claude Cowork

This is an important distinction. Most indie hackers who run Claude Code manually are not affected. The change hits developers who have automated workflows: CI pipelines, scheduled agents, GitHub Actions, or custom scripts that call Claude programmatically.

How Much Credit Do You Get?

The credit amount matches your subscription price:

Credits are per-user, non-rollover, and billed at API rates when consumed. At Sonnet 4.6 pricing, $20 in credit covers roughly 6.6 million input tokens or 1.3 million output tokens. That sounds like a lot until you realize that agentic workflows with large context windows can burn through 100,000-200,000 tokens per session.

When your credit runs out, one of two things happens:

• If you have extra usage enabled: additional Agent SDK calls flow to extra usage billing at full API rates.
• If you do not have extra usage enabled: Agent SDK requests stop until your credit refreshes next billing cycle.

Credits must be claimed before June 15 by following instructions Anthropic will send to your account email.

Why Is This Happening?

Anthropic's first-party tools like Claude Code and Claude Cowork are engineered to maximize prompt cache hit rates, reusing previously processed context to reduce compute costs. Third-party agents bypass this optimization, meaning every call processes context from scratch.

Some subscribers were paying $20 to $200 per month while consuming hundreds to thousands of dollars in token value through third-party automation. Boris Cherny, head of Claude Code at Anthropic, described it bluntly: third-party tools operating outside the cache system are "really hard to do sustainably."

The credit system ends the compute arbitrage era, where a $20 Pro subscription could run agent workflows that would cost $500 on a direct API key.

What Developers Are Saying

The reaction from the developer community is largely negative, framed around the difference between "new credits" and "reduced value."

Theo Browne, founder of T3.gg, warned that anyone using tools like Conductor, Zed, or claude -p in CI scripts has effectively had their usage cut by 25x due to the removal of subscription subsidization. He noted he now has to make the Claude Code experience on T3 Code "significantly worse" to avoid burning through the new credit ceiling.

Ben Hylak, CTO of Raindrop.ai, questioned whether the move signals compute constraints at Anthropic: "This is either really silly, or shows how bad of a spot Anthropic is in re: GPUs."

On Hacker News, one Max plan subscriber noted that 99% of their usage is non-interactive and that post-June 15 pricing "will far, far exceed what I can afford."

Anthropic engineer Lydia Hallie pushed back on the framing: "You don't pay extra. It's the same subscription, same price per month. Interactive limits unchanged. Programmatic gets a new $20-$200 included credit."

Both readings are technically accurate. The subscription price has not changed. The value delivered per dollar for heavy programmatic users has dropped significantly.

What Should You Do Before June 15?

The right response depends on how you use Claude:

You use Claude Code interactively (manual terminal sessions). Do nothing. Your workflow is unchanged and your subscription limits are not affected.

You use claude -p in scripts or CI pipelines occasionally. Claim your Agent SDK credit before June 15. At $20-$200 per month in credit, occasional automation will likely stay within the credit ceiling. Monitor usage after June 15 to see where you land.

You use Claude Code GitHub Actions on a few repos. Same as above. Claim the credit, watch your usage after the changeover. GitHub Actions sessions tend to be shorter and more task-focused than interactive sessions, so the credit may go further than you expect.

You use Conductor, Zed, Jean, OpenClaw, or another third-party agent as your primary interface. Your economics have changed. Run the numbers on your typical monthly usage, convert it to API token costs (Sonnet 4.6: $3 per million input, $15 per million output), and compare against your credit ceiling. If your usage regularly exceeds the credit, moving to a direct API key on the Developer Platform is the more predictable path.

You run shared production automation that multiple team members rely on. Anthropic is explicit: the Agent SDK credit is "sized for individual experimentation and automation." For shared production workflows, move to an API key. The Developer Platform gives you pay-as-you-go billing without per-user credit ceilings.

Worth connecting this to the rate limit increase Anthropic rolled out last month. That change gave interactive users more headroom, while this one pulls back the ceiling on programmatic usage. The two moves together paint a clear picture of where Anthropic wants the subscription model to land.

What Is the Bigger Signal Here?

This is the third significant subscription change from Anthropic in six weeks: the third-party agent ban on April 4, the brief Claude Code removal from Pro on April 21, and now the Agent SDK credit split on May 14.

The pattern points to one thing: Anthropic built subscription pricing when Claude Code was a lighter workload. Agentic workflows have changed the cost structure dramatically, and the flat-rate subscription model is being recalibrated to match.

For indie hackers who use Claude Code primarily as an interactive coding assistant, this changes nothing. For developers who have built automation infrastructure on top of Claude subscriptions, June 15 is a billing decision deadline.

The Agent View launched just two days ago gives a sense of where Anthropic is pushing Claude Code: more interactive, more managed, more first-party. The subscription model is being shaped to match that direction.

Check your usage patterns now. Claim your credit before June 15. If your automation runs heavy, price out the API alternative before the credit runs out mid-month.