{"version":"2.1.323","anchor":"policy-env-handling-org-aws-values-policy-transport-env-c","canonical_anchor":"policy-env-handling-org-aws-values-policy-transport-env-c","heading":"Remote sessions ignore a custom sign-in address set in settings files","tier":"notice","area":"Settings","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/policy-env-handling-org-aws-values-policy-transport-env-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Remote sessions ignore a custom sign-in address set in settings files\n\nWith CLAUDE_CODE_REMOTE true, settings files can no longer set CLAUDE_CODE_CUSTOM_OAUTH_URL, and organization AWS values are kept apart\n\n**What**\n\nSettings files can set environment variables for Claude Code. Several things changed in how that works:\n\n- When `CLAUDE_CODE_REMOTE` is true, no settings file can set `CLAUDE_CODE_CUSTOM_OAUTH_URL`, the custom sign-in address. A warning says so and tells you to set it in the environment Claude Code is started with instead.\n\n- AWS values supplied by your organization are now tracked separately from values you set yourself.\n\n- Environment values from your organization's policy that control how Claude Code connects are now carried through.\n\n**Why**\n\nSettings managed by your organization now take priority over your own or a repository's settings for AWS credentials and connection settings. In remote sessions, a custom sign-in address has to come from the starting environment.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}