9 people reported
All time, since Sep 22, including 7 thumbs-up on GitHub.
Desktop engine stuck on old build
“The standalone CLI on the same machine is on 2.1.280 and offers Opus 5.5 without any problem, which isolates this to the Desktop app's bundled component.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/claude-code/issues/1746/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Desktop app's embedded Claude Code engine stuck on old build. Code tab model picker greys out Opus 5.5 while the app's update check reports "You're up to date" or "latest version".
Is this your bug?
File my report- Where
- Desktop app Code tab
- Error text
Update to 2.1.280+ to use Opus 5.5.- Versions
- 2.1.260
- Platforms
- macOS
- How bad
- Breaks a normal workflow.
Not quite your bug?
Original reports2, newest first
- Desktop app "Check for Updates" reports current when embedded Claude Code engine is stale, blocking Opus 5.5/Sonnet 5.5#98989
- macOS 12: Desktop app stuck on bundled Claude Code 2.1.260, Opus 5.5 greyed out — yet 2.1.280 lists this app's SDK wrapper (0.3.260) as tested while
stable(2.1.267) does not#96105