{"version":"2.1.265","anchor":"gateway-session-messaging-simplifiedunified-for-remote-cont","canonical_anchor":"gateway-session-messaging-simplifiedunified-for-remote-cont","heading":"Gateway session messaging simplified\/unified for Remote Control","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/gateway-session-messaging-simplifiedunified-for-remote-cont","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Gateway session messaging simplified\/unified for Remote Control\n\nRemote Control's gateway-blocked message is now a single generic explanation instead of two separate cases\n\n**What**\n\nWhen a Claude Code session can't use Remote Control because it's routed through an enterprise or cloud gateway, it now shows one generic message saying the session uses a gateway that doesn't support Remote Control. Previously this distinguished between a session signed in via `\/login` to an enterprise cloud gateway and one set up via the `CLAUDE_CODE_USE_GATEWAY` environment variable.\n\n**Why**\n\nThis simplifies the explanation shown to users, though the underlying limitation, that gateway-routed sessions can't use Remote Control, is unchanged.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}