{"version":"2.1.300","anchor":"cloud-session-creation-has-a-separate-console-profile-path","canonical_anchor":"cloud-session-creation-has-a-separate-console-profile-path","heading":"Cloud sessions gain a sign-in path for Console organizations","tier":"notice","area":"Auth","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/cloud-session-creation-has-a-separate-console-profile-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Cloud sessions gain a sign-in path for Console organizations\n\nStarting a cloud session can now open a browser sign-in for your Console organization instead of requiring a claude.ai login\n\n**Unclear.** It is not clear which accounts or conditions make Claude Code take the Console sign-in route.\n\n**What**\n\nWhen 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.\n\nIf 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.\"\n\n**Why**\n\nCloud 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.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: no"}