{"version":"2.1.269","anchor":"remote-session-commands-visibility-gate-simplified","canonical_anchor":"remote-session-commands-visibility-gate-simplified","heading":"Remote-session commands' visibility gate simplified","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/remote-session-commands-visibility-gate-simplified","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Remote-session commands' visibility gate simplified\n\nRemote-session commands now use a single visibility check instead of two combined checks\n\n**Unclear.** Whether the simplified check changes visibility outcomes in any real scenario, versus just consolidating the same logic, is not stated.\n\n**What**\n\nThe commands for `remote-env` and cloud sessions used to appear only when two separate checks both passed: a base check plus an explicit policy flag called `allow_remote_sessions`. Now a single combined check controls whether these commands show up.\n\n**Why**\n\nThis simplifies how Claude Code decides whether to show remote-session related commands, though the practical effect for most users should be the same as before.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}