Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix 1M context window removed from Opus 4.6 API billing users — regression [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52187•Fetched 2026-04-23 07:34:17
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
aadilk96aadilk96
Participants
aadilk96aadilk96github-actions[bot]github-actions[bot]
Timeline (top)
labeled ×3commented ×1cross-referenced ×1

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.

Root Cause

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.

RAW_BUFFERClick to expand / collapse

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

extent analysis

TL;DR

The 1M context window for Opus 4.6 should be restored for API Usage Billing customers or an opt-in mechanism provided to avoid penalizing heavy users.

Guidance

  • Verify the settings.json configuration to ensure the "model": "opus[1m]" setting is correctly formatted and not overridden by other settings.
  • Check the Opus documentation for any updated configuration options or workarounds for API Usage Billing customers.
  • Consider reaching out to the development team to discuss potential alternatives, such as an opt-in mechanism for the 1M context window at a higher per-token rate.
  • Review the billing structure to understand the impact of the context window restriction on token usage and costs.

Example

No code snippet is provided as the issue is related to configuration and billing rather than code implementation.

Notes

The solution may depend on the development team's willingness to revisit the context window restriction for API Usage Billing customers. The provided guidance is based on the information given and may not be exhaustive.

Recommendation

Apply a workaround by discussing alternative solutions with the development team, as there is no clear indication of an available fix or upgrade to restore the 1M context window.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#chain error#conversation history#tool integration#LLM response

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING