You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
AuthArea: what it touches
New FeaturesKind: in v2.1.300,
What probably matters to youSection of the release
Unclear It is not clear which accounts or conditions make Claude Code take the Console sign-in route.
What
When you start a cloud session (Claude Code running on a remote machine rather than your own computer), Claude Code can now take a second route to sign you in. Before, it always used your claude.ai login. On the new route, it tells you it is opening your browser to sign in for cloud sessions with your Console organization. If the browser does not open, it offers a code you can paste instead.
If that sign-in is refused, Claude Code reports it as a refused Console profile. When the new route is not taken, the old behaviour stays: without a claude.ai login you see "Cloud sessions require a claude.ai login. Run /login to authenticate."
Why
Cloud sessions are no longer tied only to claude.ai logins, so people who sign in through an Anthropic Console organization may be able to start them too.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear which accounts or conditions make Claude Code take the Console sign-in route.
Anthropic's release notes agreeFixed a login refused by forceLoginOrgUUID leaving the refused organization's token stored, or live after /login
