Opus 4.7 1M context model option missing from /model picker after 2.1.133 upgrade

Status Fixed / completed

Reported on v2.1.133

Maintainer reply None cached

Activity 6 comments · opened May 8, 2026 · closed May 16, 2026

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.

View original on GitHub ↗

6 Comments

github-actions[bot] · 3 months ago

Found 3 possible duplicate issues:

This issue will be automatically closed as a duplicate in 3 days.

If your issue is a duplicate, please close it and 👍 the existing issue instead
To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

hariDasu · 3 months ago

what is this crap... so many hours wasted just now wondering why the quality declined. now i want to sleep. seems intentional from claude code team.

hariDasu · 3 months ago

resolved this morning after running claude update sorry for rage last night claude is the greatest developer of all time 🙏

aaaaaandrew · 3 months ago

Sharing some disassembly evidence in case it helps narrow this down — the picker regression for Bedrock users actually landed in v2.1.129, not v2.1.133, and persists through the latest version (v2.1.138 as of writing). The "fixed after claude update" comment above is consistent with a firstParty/subscription user; the firstParty picker branch still emits the Opus 4.7 (1M context) row, but the Bedrock branch does not.

The picker assembly function has separate branches per provider mode. Paraphrased from the minified binary:

v2.1.128 Bedrock branch:

if (bedrockMode) {
  T = [defaultRow]
  if (customOpus) T.push(customOpus); else if (...) T.push(Opus47Row);
  if (customSonnet) T.push(customSonnet);
  else if (proSubscription) T.push(SonnetCustomRow);
  else { T.push(SonnetRow); if (...) T.push(Opus47_1M_Row); }   // ← present
  return T;
}

v2.1.129+ Bedrock branch:

if (bedrockMode) {
  T = [defaultRow]
  if (customOpus) T.push(customOpus); else if (...) T.push(Opus47Row);
  if (customSonnet) T.push(customSonnet);
  else { T.push(SonnetRow); if (...) T.push(Sonnet_1M_Row); }   // ← Opus47_1M_Row dropped
  return T;
}

The Opus 4.7 (1M context) row builder still exists in 2.1.129+ and is referenced from the firstParty branch, but the Bedrock branch no longer pushes it. Other 1M rows (Sonnet 1M, Opus 4.6 1M) are still emitted, which is why this looks "partially broken" rather than a global 1M regression. claude update does not restore the row for Bedrock users — the gap exists in every released version since 2.1.129.

Workaround for Bedrock users who need it now: set "model": "<model-id>[1m]" (or "<bedrock-arn>[1m]") in settings.json. The active model will then carry the [1m] suffix and the existing Opus 4.7 row in the picker will render with the "(1M context)" label, even though the row itself is still the standard variant. Selecting any other row drops the suffix and there is no way to pick it back from the picker.

Versions tested: 2.1.120, 2.1.128, 2.1.129, 2.1.132, 2.1.133, 2.1.136, 2.1.137, 2.1.138.

raulp25 · 3 months ago

@hariDasu lol

github-actions[bot] · 1 month ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.