{"version":"2.1.242","anchor":"login-asks-how-you-want-to-sign-in-to-a-console-account","canonical_anchor":"login-asks-how-you-want-to-sign-in-to-a-console-account","heading":"\/login asks how you want to sign in to a Console account","tier":"use","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/login-asks-how-you-want-to-sign-in-to-a-console-account","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### \/login asks how you want to sign in to a Console account\n\n\/login now offers signing in to your Console account instead of only creating an API key.\n\n**What**\n\nChoosing \"Anthropic Console account\" in `\/login` no longer jumps straight to creating an API key. A second screen offers \"Sign in with your Console account (recommended)\" or \"Create an API key (legacy) - adds a key to your Console workspace\", plus \"Go back\". The sub-menu only appears on the first-party API with no managed policy settings, no pinned login organization, and login not forced to claude.ai; otherwise the old API-key path runs unchanged.\n\n**Details**\n\n- The check is entirely local (settings and environment), not a server-side flag.\n- Picking the non-API-key path on a machine with pinned settings fails with \"Settings on this machine pin the login method or organization, so signing in without an API key is not available here.\"\n- Two new telemetry events distinguish the choices: `tengu_oauth_console_token_selected` and `tengu_oauth_console_api_key_selected`. Neither exists in 2.1.241.\n\n**Evidence**\n\n`tengu_oauth_console_token_selected`\n\n- Area: Auth\n- Names: `\/login`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 4\/5"}