{"version":"2.1.232","anchor":"cloud-gateway-sign-in-explains-its-restart-and-refuses-when-","canonical_anchor":"cloud-gateway-sign-in-explains-its-restart-and-refuses-when-","heading":"Cloud gateway sign-in explains its restart, and refuses when it cannot","tier":"notice","area":"Cloud Gateway","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/cloud-gateway-sign-in-explains-its-restart-and-refuses-when-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Cloud gateway sign-in explains its restart, and refuses when it cannot\n\nCloud gateway sign-in explains its restart, and ends the session when a restart can't carry state.\n\n**What**\n\nAfter 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\".\n\n**Details**\n\n- Reasons for refusing include permission rules set for this session only, and launch flags.\n- Background sessions never restart: \"a background session cannot restart itself (sign in from a session started directly with `claude`)\".\n- When a restart does happen, command-line restrictions are replayed via `--allowed-tools`, `--disallowed-tools`, `--agent`, `--agents` and `--append-system-prompt`.\n\n**Evidence**\n\n`this session has restrictions a restart can't carry over`\n\n- Area: Cloud Gateway\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}