{"version":"2.1.293","anchor":"provider-selector-env-flags-now-cleared-for-awsgcpgateway","canonical_anchor":"provider-selector-env-flags-now-cleared-for-awsgcpgateway","heading":"Leftover AWS, Google Cloud and gateway provider variables are now cleared","tier":"notice","area":"Elsewhere","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/provider-selector-env-flags-now-cleared-for-awsgcpgateway","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Leftover AWS, Google Cloud and gateway provider variables are now cleared\n\nWhen Claude Code sets up a provider's environment, it now also blanks `CLAUDE_CODE_USE_ANTHROPIC_AWS`, `CLAUDE_CODE_USE_ANTHROPIC_GOOGLE_CLOUD` and `CLAUDE_CODE_USE_GATEWAY`\n\n**What**\n\nWhen Claude Code builds the environment variables for a model provider (the service that answers Claude's requests), it blanks out variables that would pick a different provider. That set now also includes:\n\n- `CLAUDE_CODE_USE_ANTHROPIC_AWS`\n\n- `CLAUDE_CODE_USE_ANTHROPIC_GOOGLE_CLOUD`\n\n- `CLAUDE_CODE_USE_GATEWAY`\n\nBefore, only the variables tied to provider command-line flags were blanked.\n\n**Why**\n\nA stray provider variable left in your environment can no longer override the provider you configured.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: yes"}