[FEATURE] Expose all API-available models in Claude Code Desktop model picker

Resolved 💬 3 comments Opened Apr 18, 2026 by rygereditsalt Closed May 27, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

The Claude Code Desktop app's model picker is server-controlled, meaning when Anthropic removes a model from the dropdown, users lose access entirely — even if that model is still available and functional via the CLI.

Currently, claude-opus-4-6 works perfectly when launched via the terminal with claude --model claude-opus-4-6, but there is no equivalent way to select it in the Desktop app. The model picker only shows what the server provides, and Opus 4.6 has been removed following the 4.7 release.

Also, in the future, it would be more convenient to have a wider selection of models in the Claude Code Desktop app

<img width="323" height="375" alt="Image" src="https://github.com/user-attachments/assets/c1a84e5f-9746-4e18-a3bd-e689d0464d34" />

Workarounds I've already tried — none work for the Desktop app:

  • Set ANTHROPIC_MODEL=claude-opus-4-6 as a permanent user-level environment variable on Windows → Desktop app ignores it, only works for terminal CLI
  • Edited ~/.claude/settings.json with "model": "claude-opus-4-6" → only affects terminal CLI, Desktop app doesn't read it
  • Checked claude_desktop_config.json in AppData/Roaming/Claude → no model override field exists
  • Checked AppData/Roaming/Claude/claude-code/ directory → no settings.json present

All of these work for the terminal CLI, confirming claude-opus-4-6 is still fully functional on the API. The Desktop app simply doesn't expose it because its model picker is server-controlled and independent from the CLI's config system.

The Desktop app and the terminal CLI are essentially two separate products sharing the Claude Code engine, but the Desktop app overrides model selection through its own UI with no way to configure it locally.

Proposed Solution

Expose all API-available models in the Claude Code Desktop model picker — not just the latest version. Models like claude-opus-4-6, claude-opus-4-5-20251101, and claude-opus-4-20250514 still work via the CLI but are hidden in Desktop. A simple "Show all available models" toggle in settings would let users access the full list while keeping the default dropdown clean for everyone else.

Alternative Solutions

  • Add a "model" field in claude_desktop_config.json that overrides the server-controlled picker, matching how ~/.claude/settings.json already works for the CLI
  • Allow the /model command within Desktop sessions to accept full model strings like the CLI version.

Priority

Critical - Blocking my work

Feature Category

Configuration and settings

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗