Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.242 Home All releases ←olderv2.1.241 v2.1.243newer→
Claude Code v2.1.242

/login asks how you want to sign in to a Console account

Use it now
Useful4 Signal4
Auth

/login now offers signing in to your Console account instead of only creating an API key.

/login
What

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.

Details
  • 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_selected and tengu_oauth_console_api_key_selected. Neither exists in 2.1.241.
Evidence

tengu_oauth_console_token_selected

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.242 →