[BUG] /model picker on Bedrock only shows one model per family, ignoring availableModels in settings.json

Resolved 💬 2 comments Opened Apr 23, 2026 by bolak92 Closed May 27, 2026

Preflight Checklist

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

What's Wrong?

## Environment

  • Claude Code version: (latest)
  • Provider: AWS Bedrock (CLAUDE_CODE_USE_BEDROCK=1)
  • Platform: Linux

## Description

When using Claude Code via Bedrock, the /model picker only shows one model per family
(Sonnet, Opus, Haiku), determined by the ANTHROPIC_DEFAULT_* env vars. Additional models
listed in availableModels in settings.json from the same family are silently deduplicated
and never appear in the picker.

What Should Happen?

## Expected Behavior

All models listed in availableModels should appear as selectable options in the picker,
regardless of family overlap.

## Actual Behavior

Only three entries appear — one per family, each pinned to the ANTHROPIC_DEFAULT_* env var:

  1. Default Use the default model (currently Sonnet 4.6)
  2. Custom Sonnet model
  3. Custom Opus model ← always ANTHROPIC_DEFAULT_OPUS_MODEL, not other opus variants
  4. Custom Haiku model

Models like global.anthropic.claude-opus-4-7 that belong to the same family as the default
are never shown, even when explicitly listed in availableModels.

Error Messages/Logs

Steps to Reproduce

## Steps to Reproduce

  1. Set CLAUDE_CODE_USE_BEDROCK=1 and configure ANTHROPIC_DEFAULT_OPUS_MODEL=global.anthropic.claude-opus-4-6-v1
  2. Add both global.anthropic.claude-opus-4-7 and global.anthropic.claude-opus-4-6-v1 to availableModels in

~/.claude/settings.json

  1. Run /model inside Claude Code

Claude Model

Other

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.118

Platform

AWS Bedrock

Operating System

Other Linux

Terminal/Shell

PyCharm terminal

Additional Information

_No response_

View original on GitHub ↗

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