What
Cloud sessions need you to be signed in with a claude.ai account. When you are not, the error now reads: "Cloud sessions need a claude.ai sign-in. Run claude auth login (or /login in a local session), then try again."
The message is shorter than before. It no longer mentions /status or says that API key sign-in is not enough, and /login is now offered only for local sessions.
Why
In a remote or non-interactive session you may not be able to type a slash command such as /login. The message now gives a command you can run from your terminal instead.
Names in the bundleclaude auth login/login
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Claude apps gateway for Amazon Bedrock, Claude Platform on AWS, Google Cloud, and Microsoft Foundry touched a line naming /login after this was published.
Some organizations number their internal network from a public IPv4 block they own, such as a carrier's own address space or a legacy `/8`, so their gateway has no private address. List those blocks in the `gatewayInternalNetworks` managed…claude-apps-gateway see the edit
Confirmed since
Anthropic's documentation has since written up claude auth login, on Use Claude Code in the cloud.
* ``Cloud sessions need a claude.ai sign-in. Run `claude auth login` (or /login in a local session), then try again.``claude-code-on-the-web see the edit
Confirmed since
Anthropic's documentation has since written up /login, on Use Claude Code in the cloud.
* ``Cloud sessions need a claude.ai sign-in. Run `claude auth login` (or /login in a local session), then try again.``claude-code-on-the-web see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /login, on Use Claude Code in the cloud.
Anthropic's release notes agree
Added a /status and doctor warning when managed settings ignore user-configured sandbox allowRead paths or allowed domains