Rationing: The Split

On May 13, Anthropic announced that Claude Code weekly limits are 50% higher, effective immediately, through July 13.¹ The same day, the company announced that starting June 15, paid Claude plans will receive a "dedicated monthly credit for programmatic usage" covering the Claude Agent SDK, claude -p, Claude Code GitHub Actions, and third-party apps built on the Agent SDK.²

Read those two announcements together. The first one gives you more. The second one splits how you use it.

The Gift

The 50% limit increase is temporary. It runs through July 13. It requires no opt-in. Anthropic's Reddit post, from u/ClaudeOfficial, was five sentences long: limits are higher, already applied, nothing to do.¹

This follows the May 6 announcement that Claude Code's five-hour rate limits had been doubled for Pro, Max, Team, and seat-based Enterprise plans, enabled by a compute deal with SpaceX granting Anthropic access to over 300 megawatts of capacity at the Colossus 1 data center, more than 220,000 NVIDIA GPUs.³ The May 6 doubling applied to five-hour rate limits. The May 13 boost applies to weekly limits. Different metrics, same direction.

Two limit increases in eight days. Anthropic framed both as generosity. Both preceded a structural billing change.

The Split

Starting June 15, Agent SDK usage on subscription plans will draw from a new monthly Agent SDK credit, separate from interactive usage limits.⁴

The credit covers four categories of programmatic usage: the Claude Agent SDK, the claude -p flag for headless mode, Claude Code GitHub Actions, and third-party apps built on the Agent SDK.²

When the credit runs out, additional usage flows to "extra usage" at standard API rates, but only if you have enabled extra usage. If you haven't, programmatic requests stop until the credit refreshes.⁴

Credits are per-user. They cannot be pooled, transferred, or shared across an organization.⁴

Before June 15, interactive and programmatic usage drew from the same pool. After June 15, they are separate meters. Your typing in the terminal is one budget. Your agents running in CI are another.

The Pattern

This is the sixth Rationing story we have published. Each one follows the same structure.

Anthropic rationed Claude quietly, then confessed.⁵ They moved to pay-per-overage. They introduced credits. They doubled limits with a SpaceX deal. Now they are splitting usage into interactive and programmatic pools.

GitHub did the same thing on a longer timeline. Introduced rate limits, removed models from cheaper tiers, paused signups, shipped a billing preview tool, and announced usage-based pricing for June 1. We published that story this morning.⁶

Windsurf replaced credits with quotas in March. Cursor tightened limits. The pattern is always the same: subsidize to acquire users, make the tools good enough to create dependency, then restructure the pricing to reflect actual costs. The restructuring always arrives wrapped in a gift.

Why the Split Matters

The distinction between interactive and programmatic usage is a product decision about what Claude Code is for, disguised as a billing detail.

Interactive usage is a developer typing in a terminal. The session is bounded by human attention. You type, you wait, you read, you type again. The token consumption is throttled by the speed of thought.

Programmatic usage is an agent running in a CI pipeline, a GitHub Action reviewing every pull request, a fleet of SDK-powered bots processing tickets at 3 AM. The token consumption is throttled by nothing. One developer's subscription can power dozens of automated agent sessions, each consuming tokens at machine speed.

Anthropic's CEO Dario Amodei has said publicly that the company is compute-constrained and that data-center buildouts take 18 to 24 months.⁷ The SpaceX deal bought time. The split buys structure. By separating the meters, Anthropic can price the two use cases differently without appearing to cut limits on either one.

The interactive pool stays generous. The programmatic pool gets its own budget. If your agents burn through the programmatic credit, you pay API rates or they stop. Your terminal session is unaffected. The developer who types never notices. The developer who automates does.

The Timing

The @ClaudeDevs tweet announcing the June 15 credit had 89,900 views, 116 likes, 170 retweets, and 436 bookmarks within hours of posting.² The bookmark-to-like ratio is 3.8 to 1. People are saving this to study later because the implications for their CI/CD pipelines are not immediately clear.

The 50% limit boost was posted to Reddit with no fanfare. The programmatic credit was posted to X with a product screenshot. Neither was a blog post. Neither linked to pricing page updates. Neither had a CEO quote.

The announcements that restructure billing never get blog posts. The announcements that increase limits always do.