Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Opus 4.7 1M context model option missing from /model picker after 2.1.133 upgrade

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…

After upgrading to Claude Code 2.1.133, the Opus 4.7 1M token context model option no longer appears in the /model picker. Previously the picker showed a distinct entry for the 1M context variant alongside the standard Opus 4.7 entry; now only a single "Opus" option is shown.

Root Cause

After upgrading to Claude Code 2.1.133, the Opus 4.7 1M token context model option no longer appears in the /model picker. Previously the picker showed a distinct entry for the 1M context variant alongside the standard Opus 4.7 entry; now only a single "Opus" option is shown.

RAW_BUFFERClick to expand / collapse

Summary

After upgrading to Claude Code 2.1.133, the Opus 4.7 1M token context model option no longer appears in the /model picker. Previously the picker showed a distinct entry for the 1M context variant alongside the standard Opus 4.7 entry; now only a single "Opus" option is shown.

Environment

  • Claude Code version: 2.1.133
  • OS: Windows 11 Enterprise (10.0.26100)
  • Shell: bash

Expected behavior

Be able to select the Opus 4.7 1M context window variant from the /model picker, or have a documented way to opt into it (env var, settings.json field, model ID).

Actual behavior

Only a single "Opus" entry is shown in /model. No visible option for the 1M context variant.

Notes

The v2.1.128 changelog mentions the model picker was updated to collapse duplicate Opus 4.7 entries. It looks like the 1M variant may have been folded into that consolidation rather than intentionally removed. If it's still accessible via a model ID or config setting, documenting that would help; otherwise restoring the picker entry would be appreciated.

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…

FAQ

Expected behavior

Be able to select the Opus 4.7 1M context window variant from the /model picker, or have a documented way to opt into it (env var, settings.json field, model ID).

#tool integration#LLM response#prompt template#agent execution#callback error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING