[BUG] /model persists us. prefix for Opus 4.6 on EU Bedrock (eu-west-1), causing 400 in new sessions

Status Fixed / completed
Reported on v2.1.100
Maintainer reply None cached
Activity 4 comments · opened Apr 10, 2026 · closed Apr 10, 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?

When using AWS Bedrock in eu-west-1, running /model and selecting Opus 4.6 writes us.anthropic.claude-opus-4-6-v1 into ~/.claude/settings.json. This model ID is invalid in eu-west-1 — only eu.anthropic.claude-opus-4-6-v1 and global.anthropic.claude-opus-4-6-v1 exist there.

The session where /model was used continues to work (presumably resolves the model differently at runtime), but every new session reads the persisted us. model ID from settings.json and fails with:

API Error (us.anthropic.claude-opus-4-6-v1): 400 The provided model identifier is invalid.

Sonnet 4.6 is unaffected — /model correctly persists eu.anthropic.claude-sonnet-4-6 for Sonnet.

Expected Behavior

/model should persist either:

  • The short alias (opus) and resolve the regional prefix at runtime, OR
  • The correct regional prefix (eu. when AWS_REGION=eu-west-1)

Steps to Reproduce

  1. Configure Bedrock with AWS_REGION=eu-west-1:

``json
{
"env": {
"CLAUDE_CODE_USE_BEDROCK": "1",
"AWS_REGION": "eu-west-1",
"AWS_PROFILE": "your-profile"
}
}
``

  1. Start Claude Code, run /model, select Opus 4.6
  2. Send any message — works in this session
  3. Check ~/.claude/settings.json — shows "model": "us.anthropic.claude-opus-4-6-v1"
  4. Open a new Claude Code session — fails with 400

Verification

# Only eu. and global. profiles exist in eu-west-1:
aws bedrock list-inference-profiles --region eu-west-1 \
  --query 'inferenceProfileSummaries[?contains(inferenceProfileId,`opus-4-6`)].inferenceProfileId'
# ["eu.anthropic.claude-opus-4-6-v1", "global.anthropic.claude-opus-4-6-v1"]

Environment

  • Claude Code version: 2.1.100 (bug NOT present in 2.1.97)
  • API provider: Amazon Bedrock
  • AWS region: eu-west-1
  • OS: macOS Darwin 25.3.0
  • Shell: zsh

Related Issues

  • #20594 — ANTHROPIC_MODEL ignored, cross-region inference profile used instead
  • #27241 — Haiku model ID missing cross-region prefix
  • #25193 — Teammates receive normalized model ID instead of Bedrock model ID

View original on GitHub ↗

4 Comments

github-actions[bot] · 6 months ago

Found 1 possible duplicate issue:

  1. https://github.com/anthropics/claude-code/issues/23499

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

siemens-TAG · 6 months ago

Not a duplicate of #23499. That issue is about the [1m] (1M context) variant specifically. This bug affects the standard Opus 4.6 selection — no 1M variant involved.

Regression from 2.1.97 → 2.1.100

  • 2.1.97: /model → Opus 4.6 works correctly, persists eu.anthropic.claude-opus-4-6-v1
  • 2.1.100: /model → Opus 4.6 persists us.anthropic.claude-opus-4-6-v1 — invalid in eu-west-1

Impact

Opus 4.6 is completely broken for all EU Bedrock users. Any user in eu-west-1, eu-west-3, or eu-central-1 who switches to Opus via /model will:

  1. Have their settings.json poisoned with an invalid us. prefix model ID
  2. Every subsequent new session fails with 400 The provided model identifier is invalid
  3. Must manually edit settings.json to recover

This is not an edge case — it affects every EU Bedrock deployment. Requesting regression label.

siemens-TAG · 6 months ago

Still broken in 2.1.101 — same behavior, /model → Opus 4.6 persists us.anthropic.claude-opus-4-6-v1 on eu-west-1.

github-actions[bot] · 5 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.