{"version":"2.1.273","anchor":"new-machine-lane-floor-version-check-for-remote-control-se","canonical_anchor":"new-version-floor-check-declines-bridge-sessions-on-outdated","heading":"Remote Control sessions now decline outdated machines via a version floor check","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/new-machine-lane-floor-version-check-for-remote-control-se","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Remote Control sessions now decline outdated machines via a version floor check\n\nClaude Code declines Remote Control bridge sessions when the local machine's version is below a server-set minimum\n\n**What** Before starting or attaching to a Remote Control (bridge) session, Claude Code now checks a version floor: a minimum CLI version required for that session, advertised by the server. If the machine's own Claude Code build is older than that floor, or the floor can't be read (unanswered or malformed), the machine declines the session instead of trying to run it, logging a message like \"Declined session ...\" or \"Remote Control could not attach: ...\".\n\nA new telemetry event, `bridge_machine_lane_floor`, fires when this happens, with a reason of `below_floor`, `floor_malformed`, or `floor_unanswered`.\n\n**Why** This stops an out-of-date Claude Code install from silently trying to run a Remote Control session it isn't equipped to handle, and gives a clear signal (in logs and telemetry) when that happens.\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"}