[FEATURE] Regional Model Selection in Claude Code

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

That's an excellent feature request! Here's a draft you can submit to Anthropic:

---

Feature Request: Regional Model Selection in Claude Code

Problem:
When using /model in Claude Code with AWS Bedrock, users cannot easily distinguish between US-specific and global model endpoints. This causes issues for organizations with SCPs (Service Control Policies) that restrict operations to US regions only.

Proposed Solution

Current Behavior:

• /model shows: "Default (recommended)", "Opus 4.5", "Haiku", etc.
• Behind the scenes, some map to global.anthropic.* prefixes which violate region-restricted SCPs
• Users get cryptic 403 errors with no clear indication the issue is region-related

Requested Behavior:
Display regional variants explicitly in the /model menu:

1. Sonnet 4.5 (US)     - us.anthropic.claude-sonnet-4-5-*
2. Sonnet 4.5 (Global) - global.anthropic.claude-sonnet-4-5-*
3. Haiku 4.5 (US)      - us.anthropic.claude-haiku-4-5-*
4. Haiku 4.5 (Global)  - global.anthropic.claude-haiku-4-5-*
5. Opus 4.5 (US)       - us.anthropic.claude-opus-4-5-*
6. Opus 4.5 (Global)   - global.anthropic.claude-opus-4-5-*

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

API and model interactions

Use Case Example

Use Case:
US firms with compliance requirements (FedRAMP, ITAR, data sovereignty) commonly use SCPs to enforce US-only resource access. Clear regional labeling would prevent configuration issues and make Claude Code more enterprise-friendly.

Additional Context

Additional Enhancement:
Add environment variable like CLAUDE_CODE_PREFER_REGION=us to default to regional endpoints.