{"version":"2.1.296","anchor":"cloud-session-availability-message-names-the-credential-in-u","canonical_anchor":"cloud-session-availability-message-names-the-credential-in-u","heading":"Cloud sessions message names the key or token whose organization was checked","tier":"notice","area":"Cloud Sessions","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/cloud-session-availability-message-names-the-credential-in-u","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Cloud sessions message names the key or token whose organization was checked\n\nWhen cloud sessions are blocked by organization policy, the message now says which API key or token Claude Code checked the policy for\n\n**What**\n\nCloud sessions are Claude Code sessions that run on Anthropic's servers instead of on your own computer. When your organization's policy does not allow them, Claude Code shows a message beginning \"Cloud sessions aren't available with\". That message has changed.\n\nIf the session is signed in with one of these, the message now names it and says Claude Code checked the policy for the organization that key or token belongs to:\n\n- `ANTHROPIC_API_KEY`, an environment variable holding an API key\n\n- `ANTHROPIC_AUTH_TOKEN`, an environment variable holding an access token\n\n- a key produced by `apiKeyHelper`, a setting that runs your own command to supply the key\n\nWhen Claude Code is connected through a provider other than Anthropic itself, it shows a different message.\n\n**Why**\n\nIf a key or token from another organization is set on your machine, the policy that was checked may not be your own organization's. The message now tells you which credential was used, so you can see why cloud sessions are blocked and which setting to change.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}