{"version":"2.1.321","anchor":"oauth-scope-registration-cleared-when-claude-code-custom-oau","canonical_anchor":"oauth-scope-registration-cleared-when-claude-code-custom-oau","heading":"Setting a custom sign-in address now clears the default sign-in permissions","tier":"notice","area":"Auth","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/oauth-scope-registration-cleared-when-claude-code-custom-oau","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Setting a custom sign-in address now clears the default sign-in permissions\n\nWhen CLAUDE_CODE_CUSTOM_OAUTH_URL is set, Claude Code turns off all default sign-in permission requests and records that variable as the reason\n\n**What**\n\nOAuth is the sign-in method Claude Code uses, and scopes are the permissions it asks for when you sign in. When the environment variable `CLAUDE_CODE_CUSTOM_OAUTH_URL` is set, so that Claude Code signs in through a different address, the scope settings now turn every default permission request off. They also record `CLAUDE_CODE_CUSTOM_OAUTH_URL` as the reason the defaults were cleared.\n\n**Why**\n\nIf you use a custom sign-in address, expect the default permissions not to be requested.\n\n- Area: Auth\n- Names: `CLAUDE_CODE_CUSTOM_OAUTH_URL`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: yes"}