Claude Code v2.1.51 changed 1M context billing without notification

What changed in Claude Code v2.1.51

Anthropic released Claude Code v2.1.51 with a significant billing change that wasn't announced in changelogs, emails, or in-app notifications. The only visible indication was a "Billed as extra usage" label added to 1M context models in the model picker.

How billing changed

Before v2.1.51, the billing flow worked like this:

• Subscription budget → (exhausted) → Extra Usage kicks in

After v2.1.51, the billing flow changed to:

• Any call with >200K context → tokens above 200K go straight to Extra Usage
• Subscription capacity still available? Doesn't matter

This means that using 1M context models as intended—where conversation history and tool results naturally accumulate—now inevitably generates Extra Usage charges, regardless of remaining subscription capacity.

Evidence from user investigation

A Max plan subscriber ($100/month) conducted a detailed billing investigation documented in GitHub issue #28927. They analyzed JSONL session transcripts with per-call token breakdowns and day-by-day version comparisons.

Key findings:

• Before update (v2.1.49/50): 2,771 API calls, 626 calls over 200K context, 263M cache read tokens → $0 Extra Usage
• After update (v2.1.52/53): 794 API calls, 209 calls over 200K context → $48.79 Extra Usage

The workload decreased by two-thirds while the bill increased substantially.

Practical implications

You can't catch these charges in real-time. The Extra Usage meter has approximately a 24-hour delay. Users monitoring both meters during sessions see no change until charges materialize the next morning.

The Max plan explicitly includes 1M context models, but this billing change effectively makes 1M context a paid add-on that bypasses subscription allocation.