Rapls

Posted on Jun 11 • Originally published at zenn.dev

Claude's June 15 billing split: are you even affected? A solo dev's triage

#ai #claude #productivity #webdev

A line went across my timeline: "is unlimited Claude Code over?" My stomach dropped for a second. There's a billing change on June 15, and I run Claude Code every day, so the first thing I wanted to know was whether it hits my wallet.

Here's the short version. If you mostly use Claude Code interactively in a terminal, like me, you're probably fine. The change targets people who call Claude automatically. This post sorts out which side you're on, and what to check before June 15. It's also a follow-on to what I wrote about token economics.

Where this stands

Numbers and specs shift, so treat the below as true when I checked. The source of truth is Anthropic's Help Center; the announcement landed May 13-14, 2026 (via @ClaudeDevs), effective June 15. The amounts and scope below match the write-ups from The New Stack, InfoWorld, and Zed. Verify against the Help Center and your own billing screen before you act. Sources at the end.

What changes

Claude billing splits into two pools: interactive and programmatic.

Interactive use stays exactly as it is now:

Claude.ai chat
Claude Code run directly in your terminal
Claude Cowork

What moves to a separate monthly credit is programmatic use, where something calls Claude on its own:

Claude Agent SDK
claude -p (the headless, no-screen way to run Claude Code)
Claude Code GitHub Actions
Third-party agents over ACP (Zed and others)

This is a carve-out for automation, not a price hike. Your subscription limits themselves don't change.

First: are you even affected?

Sort yourself before anything else.

You're not affected if your usage looks like this:

You drive Claude Code by hand in a terminal
You chat on Claude.ai
You use Cowork

If you're the one sitting at the screen, typing and reading replies, nothing changes. No need to panic.

You are affected if Claude runs while you're not watching:

A CI pipeline calls Claude
A cron job runs claude -p on a schedule
GitHub Actions has Claude Code wired in
A third-party tool like Zed reaches Claude over ACP

The quickest way to find out is to grep across your repos, CI config, and cron for any path that calls Claude programmatically.

# look for any automated path that calls Claude
grep -rn -E "claude -p|claude_agent_sdk|anthropic" \
  ~/projects .github/workflows ~/.config 2>/dev/null

# check cron too
crontab -l 2>/dev/null | grep -i claude

No hits, and you can be fairly sure you're on the interactive-only side. A hit, and that's the path moving to separate billing.

What the separate credit looks like

The credit you move onto works like this. Monthly, per plan: $20 for Pro, $100 for Max 5x, $200 for Max 20x. Consumption is metered at standard API rates, with no rollover, per user, reset each billing cycle.

When you exhaust it, automation stops by default. If you don't want it to stop, enable the overflow setting (officially called "usage credits") so usage past the credit bills at API rates instead of being rejected. Stop, or pay and keep going: your call. Note that standard Enterprise seats don't get the credit at all, and the Help Center suggests shared production automation use Claude Platform pay-as-you-go API billing rather than subscription auth.

What to do before June 15

If you landed on the affected side:

Audit your last 30 days of programmatic use. How many claude -p scripts, Actions, scheduled jobs, and third-party tools are running, and how hard do they hit Claude? You can't judge whether the credit is enough without this.
Claim the credit. Anthropic is said to send a claim email, so claim it once from your account before June 15.
Decide on overflow. For automation you don't want stopping, turn on "usage credits." For jobs that can stop, leave it off and stay inside the credit.
Move heavy, steady automation to a direct API key (pay-as-you-go). The monthly cost becomes predictable and the tracking is cleaner. The Help Center recommends this for shared production automation.
Use prompt caching. Cache hits drop the input cost a lot (roughly a tenth of the rate), so repetitive automation stretches the credit much further. This is the same "send fewer tokens" idea from the token-economics piece.

Subscription credit, or direct API?

Which way you lean comes down to how much automation you run.

Light automation (a job that runs a few times a month) is usually fine on the included credit. Managing a separate API key would cost you more effort than it saves.
Heavy automation (runs daily, steady high volume) is better on direct API metering. It's predictable, and the Help Center steers shared production work there.

Subscription credit either stops or overflows into API charges once you cross it. If your volume is already predictable, metered API from the start is easier on the heart.

Why this happened

The reasoning is fairly plain. A human using Claude interactively sends dozens of prompts a day. An autonomous agent can fire thousands of requests, run tests in a loop, and call itself recursively. Measuring both in one subscription pool stopped making sense. Zed estimated subscriptions were subsidizing agent usage by roughly 15 to 30 times versus API pricing, and the split closes that gap. It's also the third billing adjustment around programmatic use in 2026: January's OAuth-token block (reversed within days after backlash), February's terms change, April's tighter limits, and now this.

A note to my next self

What clicked for me is that this is a line, not a price hike. Interactive use, the kind you watch, stays on the subscription. Automation, the kind that runs while you're not looking, moves to its own meter. An AI tool moved one foot from a tidy subscription to something you manage as cost infrastructure.

So the first move isn't to rush a migration, it's to see which side you're on. Interactive only, and nothing changes. Automation in the mix, and you audit the volume, then choose credit or direct API. It's the same thread as the token bill landing in someone's wallet. I run a couple of small automations myself, so before June 15 I'll grep my own setup and take inventory.

References

Verify current numbers on the official pages. The source of truth is Anthropic's Help Center.

Originally written in Japanese on Zenn. I build WordPress plugins.

DEV Community