{"version":"2.1.251","anchor":"custom-oauth-endpoints-keyed-to-a-single-environment-variabl","canonical_anchor":"custom-oauth-endpoints-keyed-to-a-single-environment-variabl","heading":"Custom OAuth endpoints keyed to a single environment variable","tier":"use","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/custom-oauth-endpoints-keyed-to-a-single-environment-variabl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Custom OAuth endpoints keyed to a single environment variable\n\nOne env var now decides your custom OAuth endpoint, and it passes to spawned commands.\n\n**What**\n\nA custom OAuth endpoint is now recognised purely from the `CLAUDE_CODE_CUSTOM_OAUTH_URL` environment variable, with the secondary fallback check removed. The same variable is also registered in the list the subprocess environment builder knows about, so it is carried as a recognised Claude Code variable when Claude Code spawns commands.\n\n**Details**\n\n- Setting `CLAUDE_CODE_CUSTOM_OAUTH_URL` is the only way to be treated as having a custom OAuth endpoint; unset means the standard endpoint is used.\n- The variable is now a known name to the code that assembles environment variables for spawned subprocesses, rather than an unrecognised passthrough.\n- Nothing else in this build shows what a spawned process does with the value once it receives it.\n\n**Evidence**\n\n`CLAUDE_CODE_CUSTOM_OAUTH_URL !== void 0`, `\"CLAUDE_CODE_CUSTOM_OAUTH_URL\"`\n\n- Area: Auth\n- Names: `CLAUDE_CODE_CUSTOM_OAUTH_URL`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}