Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [FEATURE] Allow custom/enterprise model IDs to appear in `/model` interactive picker [1 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#47164•Fetched 2026-04-13 05:39:45
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
jappaddyjappaddy
Participants
jappaddyjappaddy
Timeline (top)
labeled ×3

Fix Action

Fix / Workaround

Additional Context

  • Workaround: /model <full-model-id> works, but requires memorizing the exact ID each time.
  • The current model is saved in settings.json ("model" field), so the infrastructure for custom IDs already exists.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

Problem Statement

When using enterprise or custom model IDs (e.g., IDs with non-standard prefixes provided by enterprise API deployments), these models do not appear in the interactive /model picker.

Users can still set them via /model <custom-model-id> or settings.json, but they are excluded from the interactive selection list.

Proposed Solution Add a customModels field to settings.json that allows users to register additional model IDs for display in the /model picker:

Proposed Solution

Add a customModels field to settings.json that allows users to register additional model IDs for display in the /model picker:

{ "customModels": [ "custom-model-id-sonnet", "custom-model-id-opus" ] }

Alternative Solutions

  • When /model is invoked, query the API for accessible models and display all that are available to the authenticated team/org.
  • Allow inline search in the picker so users can type a partial model ID and match custom models.

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

Enterprise API deployments often provide model IDs with custom prefixes (e.g., "XXXX-claude-4-6-sonnet-v1") that map to standard Claude models. Switching between Sonnet and Opus variants is a common workflow, and the current picker doesn't support them, adding unnecessary friction.

Additional Context

  • Workaround: /model <full-model-id> works, but requires memorizing the exact ID each time.
  • The current model is saved in settings.json ("model" field), so the infrastructure for custom IDs already exists.

Additional Context

No response

extent analysis

TL;DR

Add a customModels field to settings.json to register additional model IDs for display in the /model picker.

Guidance

  • Consider adding the proposed customModels field to settings.json with an array of custom model IDs, such as ["custom-model-id-sonnet", "custom-model-id-opus"].
  • Alternatively, explore querying the API for accessible models when /model is invoked to display all available models to the authenticated team/org.
  • To verify the fix, check if the custom models appear in the interactive /model picker after adding them to settings.json.
  • If the proposed solution is not feasible, consider allowing inline search in the picker for users to type a partial model ID and match custom models.

Example

{
  "customModels": [
    "XXXX-claude-4-6-sonnet-v1",
    "XXXX-claude-4-6-opus-v1"
  ]
}

Notes

The proposed solution assumes that the infrastructure for custom IDs already exists, as the current model is saved in settings.json. However, the implementation details of the customModels field and its integration with the /model picker are not provided.

Recommendation

Apply workaround by adding the customModels field to settings.json, as it provides a straightforward solution to display custom models in the /model picker.

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…
#api#environment variable#network issue#logging issue#authentication issue

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [FEATURE] Allow custom/enterprise model IDs to appear in `/model` interactive picker [1 participants]