{"version":"2.1.274","anchor":"cloud-gateway-settings-failures-now-carry-a-structured-reaso","canonical_anchor":"cloud-gateway-settings-failures-now-carry-a-structured-reaso","heading":"Cloud gateway settings failures now carry a structured reason and forbidden flag","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/cloud-gateway-settings-failures-now-carry-a-structured-reaso","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Cloud gateway settings failures now carry a structured reason and forbidden flag\n\nCloud gateway settings-load failures now report a specific reason and a 'forbidden' flag\n\n**What**\n\nWhen Claude Code's cloud gateway fails to load settings, the failure result now includes a `forbidden` boolean and a `reason` field, set to one of `gateway_signin_required`, `gateway_access_denied`, or `remote_settings_required_unavailable`. These are added alongside the existing `exitMessage` and `endedSession` fields, and cover the 401 (unauthorized), 403 (forbidden), and other error cases.\n\n**Why**\n\nThis gives more precise, structured information about why a settings load failed, which should make it easier to distinguish an access-denied case from a sign-in problem or an unavailable service.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}