{"version":"2.1.229","anchor":"login-warns-if-an-oauth-token-is-set-in-your-environment","canonical_anchor":"login-warns-if-an-oauth-token-is-set-in-your-environment","heading":"\/login warns if an OAuth token is set in your environment","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/login-warns-if-an-oauth-token-is-set-in-your-environment","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### \/login warns if an OAuth token is set in your environment\n\nAfter logging in, you're warned if an OAuth token in your environment will override it later.\n\n**What**\n\nAfter a successful login, if `CLAUDE_CODE_OAUTH_TOKEN` was set when `\/login` started and the gateway is not in use, the success message now notes that new sessions will keep using the old token until you remove it from your shell profile or settings file.\n\n**Details**\n\n- Message begins `Note: CLAUDE_CODE_OAUTH_TOKEN was set in your environment when \/login started.`\n- Helpers were added alongside to re-run the bypass-permissions and auto-mode checks after login.\n\n**Evidence**\n\n`Note: CLAUDE_CODE_OAUTH_TOKEN was set in your environment when \/login started.`\n\n- Area: Auth\n- Names: `CLAUDE_CODE_OAUTH_TOKEN`, `\/login`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}