1M context window removed from Opus 4.6 API billing users — regression

Summary

With the release of Opus 4.7, the 1M context window that was previously available on Opus 4.6 has been removed for API Usage Billing customers. This is a regression for paying users.

What changed

• Before (v2.1.117): Opus 4.6 showed "1M context" in the startup banner and functioned with a 1M context window. The opus[1m] model flag in settings.json worked.
• After (v2.1.118): The 1M context window is no longer available on Opus 4.6. The opus[1m] setting in settings.json is silently ignored. 1M context is now gated behind the Max subscription plan (Opus 4.7 only).

Why this is a problem

API billing customers pay per token. We are literally paying for every token of context we consume. Restricting the context window to push a flat-rate subscription plan penalizes your heaviest and most engaged users.

This is especially impactful for users working on large, context-heavy projects where the auto-loaded project rules, architecture docs, and issue trackers consume a significant portion of the 200K window before any actual work begins.

Request

Restore the 1M context window for Opus 4.6 on API Usage Billing, or provide an opt-in mechanism (even at a higher per-token rate). Customers who pay per token should not have capabilities removed to upsell a subscription tier.

Environment

• Claude Code v2.1.117 → v2.1.118
• Model: Opus 4.6
• Billing: API Usage Billing
• OS: macOS
• Settings: "model": "opus[1m]" configured but no longer respected