Under the hood
A new provider-managed env var list decides gateway sign-in error wording.
A new provider-managed env var list covers CLAUDE_CODE_USE_BEDROCK, CLAUDE_CODE_USE_FOUNDRY, CLAUDE_CODE_USE_ANTHROPIC_AWS, CLAUDE_CODE_USE_ANTHROPIC_GOOGLE_CLOUD, CLAUDE_CODE_USE_MANTLE, and CLAUDE_CODE_USE_VERTEX. Whether the gateway sign-in error message points users to /login or tells them no sign-in is needed now depends on whether one of these provider env vars is active and CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST is unset.
Names in the bundleCLAUDE_CODE_USE_BEDROCKCLAUDE_CODE_PROVIDER_MANAGED_BY_HOST
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up CLAUDE_CODE_USE_BEDROCK, on Claude Code gateway compatibility guide.
* **Amazon Bedrock or Agent Platform format**: the developer sets `CLAUDE_CODE_USE_BEDROCK=1` with `ANTHROPIC_BEDROCK_BASE_URL`, or `CLAUDE_CODE_USE_VERTEX=1` with `ANTHROPIC_VERTEX_BASE_URL`, pointing at your gateway. Claude Code uses tha…llm-gateway-protocol see the edit
Confirmed since
Anthropic's documentation has since written up CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST, on Connect Claude Code to tools via MCP.
* Sessions on Amazon Bedrock, Claude Platform on AWS, Google Cloud's Agent Platform, or Microsoft Foundry, unless a host platform that embeds Claude Code sets [`CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST`](/docs/en/env-vars)mcp see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST, on Connect Claude Code to tools via MCP.
Anthropic's release notes agree
Changed a Claude apps gateway 403 on the managed settings load (at startup or after /login) to say Claude Code may not be enabled for the…