claude-code - 💡(How to fix) Fix [BUG] Opus 4.6 removed from Claude Desktop Code tab model picker after Opus 4.7 release [2 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#49689Fetched 2026-04-17 08:34:10
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
1
Timeline (top)
labeled ×4commented ×2
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

After the Opus 4.7 release on April 16, 2026, Opus 4.6 is no longer available in the Code tab of the Claude Desktop app (macOS). The only Opus option now resolves to Opus 4.7. There is no way to select or pin Opus 4.6 from the Code tab UI.

This issue is specific to the Code tab. The Claude.ai chat interface and Claude Cowork both still expose multiple model options in their respective model dropdowns. Only the Code tab's model picker has had Opus 4.6 removed.

Additionally, the /model command (documented for Claude Code CLI) does not work in the desktop app's Code tab, so there is no fallback to manually specify claude-opus-4-6 within the desktop interface.

Impact

Opus 4.7 ships with a new tokenizer that can produce up to ~35% more tokens for the same input text. Without the option to fall back to Opus 4.6, usage is being burned significantly faster — particularly for users on plans with message or token quotas. Users should have the ability to choose 4.6 while evaluating the cost/performance tradeoff of the new tokenizer.

Expected Behavior

Opus 4.6 should remain selectable in the Code tab's model picker alongside Opus 4.7, or at minimum, users should have a documented path to pin a specific model version from the desktop app UI — consistent with the CLI's /model claude-opus-4-6 and environment variable options.

Environment

  • Claude Desktop version: 1.3109.0
  • Platform: macOS
  • Affected surface: Code tab only (Claude.ai chat and Cowork are unaffected)

Additional Context

  • The Claude Code docs confirm /model and ANTHROPIC_MODEL env var as model pinning options, but these only apply to the CLI, not the desktop app's Code tab.
  • GitHub Changelog confirms Opus 4.7 is replacing 4.5 and 4.6 in model pickers, but no deprecation notice was shown in the desktop app UI before removal.
  • Related older issues: #34279, #36351, #40095

extent analysis

TL;DR

The issue can be mitigated by providing a way to select or pin Opus 4.6 in the Code tab of the Claude Desktop app, potentially through a UI update or a documented workaround.

Guidance

  • Investigate updating the Code tab's model picker UI to include Opus 4.6 as an option, consistent with the Claude.ai chat interface and Claude Cowork.
  • Consider adding support for the /model command in the desktop app's Code tab, allowing users to manually specify claude-opus-4-6.
  • Review the GitHub Changelog and related issues (#34279, #36351, #40095) to understand the reasoning behind removing Opus 4.6 from the model picker and potential solutions.
  • Evaluate the feasibility of adding an environment variable option, similar to ANTHROPIC_MODEL, to pin a specific model version in the desktop app.

Example

No code snippet is provided as the issue is related to UI and functionality rather than code implementation.

Notes

The solution may require updates to the Claude Desktop app's UI or backend functionality. The issue is specific to the Code tab on macOS, and the fix may not apply to other platforms or surfaces.

Recommendation

Apply a workaround by updating the Code tab's UI to include Opus 4.6 as an option or providing a documented path for users to pin a specific model version, as this would address the immediate need for users to select Opus 4.6 while evaluating the cost/performance tradeoff of the new tokenizer.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING