You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
ImprovementsKind: in v2.1.265,
ImprovementsSection of the release
What
When 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.
Why
This simplifies the explanation shown to users, though the underlying limitation, that gateway-routed sessions can't use Remote Control, is unchanged.
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed /login showing "no gateway URL is configured" when re-run in a session that signed in to a Claude apps gateway set by managed settings
