Omniscio

OmniscioGuidesNot signed in to the Cloud gateway

Claude Code: Not signed in to the Cloud gateway — run /login

Last checked against Anthropic's documentation on November 17, 2026. By the Omniscio team. Updated .

What is the exact message?

Not signed in to the Cloud gateway — run /login.

Two neighbours say related things, and both are in Anthropic's error reference beside this one:

Cloud gateway session expired — run /login to reconnect.
Administrator policy requires a Cloud gateway sign-in on this machine …

The first means a gateway sign-in existed and has run out. The second means a policy, not a missing sign-in, is refusing something else on the machine, and its full text names the credential it found instead.

What does it mean?

Your organization runs a self-hosted Claude apps gateway, which is a proxy it operates between Claude Code and the model provider. The message calls it the Cloud gateway; the docs call it the Claude apps gateway. It is one thing.

Claude Code authenticates to that gateway with a credential your organization issues instead of your personal claude.ai login.

Anthropic's instruction for that setup is one line: sign in with corporate SSO through /login, and the gateway-issued token is the session's only credential.

So this is not a broken password. It is a session that has no gateway token yet, and the message tells you the command that gets one.

Why the session has no sign-in

  • You have not signed in on this machine yet. A new install, a new profile, or a cleared config directory starts with no gateway token.
  • The gateway sign-in ran out. Anthropic's own wording for that is Cloud gateway session expired — run /login to reconnect.
  • Your Claude Code is too old for the forced sign-in. Anthropic gives v2.1.261 or later for forced gateway sign-in, and v2.1.265 or later where only the gateway URL is forced.

One neighbour is worth knowing about. If the line you see is Administrator policy requires a Cloud gateway sign-in on this machine, the policy is refusing another credential that is still on the machine, and removing it is the fix.

For any other line, the Claude Code error messages guide starts from the words on screen. Two guides cover what this page leaves alone. The login errors guide owns the rest of the sign-in family, including this message's expired-session and startup forms, and the connection errors guide starts from a request that never reached the gateway at all.

How do I fix it?

  1. Run /login in the session that shows the message. Sign in the way your organization expects, which for a gateway is your corporate identity provider rather than a personal Anthropic account.
  2. If the message names an administrator policy instead, remove the leftover key. An ANTHROPIC_API_KEY, an ANTHROPIC_AUTH_TOKEN or an apiKeyHelper is blocked at startup when managed settings require the gateway sign-in. Unset it and try again.
  3. Update Claude Code. Update to 2.1.261 or later if your version predates it. If you are on exactly 2.1.265, Anthropic records a regression that showed this message on a machine with no gateway policy at all: update to 2.1.266 or later, and you need change nothing else.

Your organization's administrator controls the other half. The gateway, its identity provider and the managed settings that point Claude Code at it are all theirs, and the message cannot be cleared from your machine alone if that policy blocks you.

How do I know it is fixed?

  • /login finishes and the terminal reports a successful sign-in.
  • /status names the credential the session is using.
  • The next message gets a real answer, and the line does not come back on the following request.

Where these answers come from

  • Anthropic's error reference, read November 17, 2026: this message and its neighbours, quoted word for word.
  • Authentication, read November 17, 2026: the Cloud gateway sign-in through /login, the gateway token as the session's only credential, and where a gateway session sits among the credential sources.
  • Connect Claude Code to an LLM gateway, read November 17, 2026: what a gateway is, and the administrator policy that forces the sign-in.

Common questions

Is a Cloud gateway the same as an LLM gateway?

No. An LLM gateway is a proxy you point Claude Code at with a base URL and a credential. The Claude apps gateway also signs developers in through your identity provider, which is why this message asks for a sign-in rather than a key.

Can I switch to my personal subscription instead?

Only if your organization's policy allows it. When managed settings force the gateway, Claude Code skips the other credential sources and asks you to sign in with /login.

What is an identity provider?

The system your organization uses to sign you in, such as its single sign-on login page. For the gateway sign-in, Anthropic says access is restricted there and not against an Anthropic organization.

Is this the same as being logged out?

No. Your claude.ai login can be perfectly good and this message still appears, because a gateway session uses the gateway token and nothing else. Signing in with a personal account does not clear it.