Applies to:
- Plan:
- Deployment:
Summary
Issue: Models listed in the Loop picker (e.g.,Claude 4.6 Sonnet) fail to work even though AWS Bedrock models like us.anthropic.claude-opus-4-5-20251101-v1:0 function correctly.
Cause: Loop’s default model picker shows Anthropic direct-API model names, which route through Anthropic’s API — not through a configured Bedrock provider.
Resolution: Add Anthropic as a separate AI provider with a valid API key, or use the full Bedrock model identifier in Loop.
Resolution steps
If you want to use the friendly model names shown in Loop (e.g., Claude 4.6 Sonnet)
Step 1: Add Anthropic as a provider
Navigate to Settings → Organization → AI providers → Anthropic, enter your Anthropic API key, and save.Step 2: Confirm models are available in Loop
Navigate to Settings → Organization → Loop and verify the Anthropic models are enabled.If you only have AWS Bedrock configured and want to stay with Bedrock
Step 1: Use the full Bedrock model identifier
When selecting a model in Loop, use the full Bedrock identifier instead of the friendly name. Example:Notes
- The Loop model picker displays Anthropic direct-API model names by default, even when only Bedrock is configured. This is a known UX issue.
- Bedrock and Anthropic direct API are separate providers. Configuring one does not enable the other.
- Org-level provider configuration is required. Project-level model settings do not apply in Loop.