{"version":"2.1.300","anchor":"cloud-session-auth-rewritten-to-a-shared-tokenorg-resolver","canonical_anchor":"cloud-session-auth-rewritten-to-a-shared-tokenorg-resolver","heading":"Cloud sessions get their sign-in and organization in a different way","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/cloud-session-auth-rewritten-to-a-shared-tokenorg-resolver","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Cloud sessions get their sign-in and organization in a different way\n\nCloud session setup now looks up your sign-in token and organization through shared code, and the missing sign-in message may read differently\n\n**Unclear.** It is not clear whether ways of signing in other than claude.ai now work for cloud sessions.\n\n**What**\n\nCloud sessions run Claude Code on remote machines. Three steps for them now look up your access token and your organization through shared code instead of reading your claude.ai sign-in directly:\n\n- fetching remote environments\n\n- creating cloud environments\n\n- listing self-hosted pools (groups of your own machines that run sessions)\n\nWhen no token is found, the error is now built by shared code rather than using the fixed message that told you to run `claude auth login`. A new error also covers failing to find your organization.\n\n**Why**\n\nIf you are not signed in, the message you see for cloud sessions may be worded differently from before.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}