Cloud gateway sign-in explains its restart, and ends the session when a restart can't carry state.
What's wrong with this entry?
After signing in through a Cloud gateway, Claude Code used to silently restart itself when managed settings failed to load or had changed. It now tells you why first ("Signed in to Cloud gateway", the failure reason, then "Restarting Claude Code to retry"), and ends the session instead of restarting when the session holds state a restart cannot carry, with the message "this session has restrictions a restart can't carry over".
- Reasons for refusing include permission rules set for this session only, and launch flags.
- Background sessions never restart: "a background session cannot restart itself (sign in from a session started directly with
claude)". - When a restart does happen, command-line restrictions are replayed via
--allowed-tools,--disallowed-tools,--agent,--agentsand--append-system-prompt.
this session has restrictions a restart can't carry over
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.227
claude gatewaynow identifies itself as the gateway providerBoth mention gateway
-
v2.1.228
Gateway runs without an OIDC block, and names two more upstream failures
Both mention gateway
-
v2.1.228
Gateway warns when no OIDC is configured and several sections are dead
Both mention gateway