{"version":"2.1.265","anchor":"cloud-gateway-sign-in-check-reworked-with-desktop-app-aware","canonical_anchor":"cloud-gateway-sign-in-check-reworked-with-desktop-app-aware","heading":"Cloud gateway sign-in check reworked with desktop-app-aware error and new required flag","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/cloud-gateway-sign-in-check-reworked-with-desktop-app-aware","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Cloud gateway sign-in check reworked with desktop-app-aware error and new required flag\n\nCloud gateway sign-in check reworked with a clearer error and desktop-app-aware handling\n\n**What**\n\nBefore using the Cloud gateway as its provider, Claude Code now checks three things instead of one: that the route is actually set to gateway, that there's no gateway authentication, and that no gateway server process is running. Previously it only checked a single administrator-policy condition.\n\nThe error message shown when not signed in now reads: \"Not signed in to the Cloud gateway - run `\/login`. (With `CLAUDE_CODE_USE_GATEWAY`, set `ANTHROPIC_BASE_URL` and `ANTHROPIC_AUTH_TOKEN`.)\" \u2014 pointing to those environment variables as an escape hatch. It also now shows a distinct error when credentials are managed by the desktop app instead.\n\n**Why**\n\nThis gives a more accurate check for whether the Cloud gateway is actually usable, and a clearer error message that tells users how to work around a sign-in problem using environment variables, or explains that their desktop app is managing credentials instead.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}