{"version":"2.1.273","anchor":"remote-control-now-enforces-a-minimum-version-floor-before-a","canonical_anchor":"remote-control-now-enforces-a-minimum-version-floor-before-a","heading":"Remote Control now enforces a minimum-version floor before accepting sessions started remotely","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/remote-control-now-enforces-a-minimum-version-floor-before-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Remote Control now enforces a minimum-version floor before accepting sessions started remotely\n\nRemote Control now checks your Claude Code version meets a minimum before accepting a remotely started session\n\n**Unclear.** Nothing has been read yet about whether the `tengu_bridge_min_version` gate is switched on for any account.\n\n**What**\n\nWhen a session is started remotely (via Remote Control), Claude Code now checks that the local installation meets a required minimum version, and distinguishes three ways that check can fail:\n\n- the required version couldn't be retrieved from the server at all\n\n- the value received from the server was malformed\n\n- the local installation is genuinely below the required version\n\nEach case now shows its own distinct message explaining what went wrong.\n\n**Why**\n\nThis makes it clearer why a remotely started session was rejected, instead of showing one generic failure for what could be three different underlying problems.\n\n- Flag `tengu_bridge_min_version`: Not enough to say (read for one account on one subscription tier against v2.1.273; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}