Choosing "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.
- The check is entirely local (settings and environment), not a server-side flag.
- 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."
- Two new telemetry events distinguish the choices:
tengu_oauth_console_token_selectedandtengu_oauth_console_api_key_selected. Neither exists in 2.1.241.
tengu_oauth_console_token_selected
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
The `/login` and `/logout` commands don't sign you into a claude.ai subscription for Claude Platform on AWS. Authentication runs through your AWS credentials or workspace API key.claude-platform-on-aws see the edit
* Added the `gatewayInternalNetworks` managed setting, letting administrators allow `/login` to a Claude apps gateway on their organization's own public IPv4 blockchangelog see the edit
Anthropic's documentation has since written up /login, on Claude Code changelog.