{"version":"2.1.234","anchor":"the-claude-code-oauth-token-login-warning-can-arrive-as-its-","canonical_anchor":"the-claude-code-oauth-token-login-warning-can-arrive-as-its-","heading":"The CLAUDE_CODE_OAUTH_TOKEN login warning can arrive as its own message","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/the-claude-code-oauth-token-login-warning-can-arrive-as-its-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### The CLAUDE_CODE_OAUTH_TOKEN login warning can arrive as its own message\n\nThe warning about a set OAuth token env var can now arrive as its own message after login.\n\n**What**\n\nLogging in while `CLAUDE_CODE_OAUTH_TOKEN` is set no longer always glues the warning onto \"Login successful\". A three-way choice now picks no warning, an inline one, or a separate notice; when the session is about to auto-retry the query that failed, the warning is delivered once as its own message.\n\n**Details**\n\n- Triggered when `CLAUDE_CODE_OAUTH_TOKEN` is set in the environment and the gateway is not active.\n- The login result formatter takes an explicit flag saying whether to include the warning, so the two paths cannot both emit it.\n\n**Evidence**\n\n`includeEnvTokenWarning`\n\n- Area: Auth\n- Names: `CLAUDE_CODE_OAUTH_TOKEN`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}