Skip to content

[BUG] Default Model does not respect availableModels setting #67349

@ArcherTsai

Description

@ArcherTsai

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 putting the following settings into managed settings of Claude Enterprise, Cluade CLI still shows "1. Default (recommended) Opus 4.7 with 1M context · Most capable for complex work" on the menu. And users can still use Opus model.

{
"availableModels": ["sonnet", "haiku"],
"model": "claude-sonnet-4-6"
}

What Should Happen?

The default recommended Opus model shouldn't appear in the list if it is not in the availableModels list. And users should not be allowed to use it.

Error Messages/Logs

Steps to Reproduce

  1. Set availableModels in the managed settings of Claude Enterprise, which does not contain Opus models.
  2. Open Claude CLI and use /model command.
  3. The model picker shows up, and Opus model is still available as a default recommended model.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.153

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

WSL (Windows Subsystem for Linux)

Additional Information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:modelbugSomething isn't workinghas reproHas detailed reproduction stepsplatform:wslIssue specifically occurs on WSL

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions