{"version":"2.1.53","anchor":"remote-control-minimum-version-enforcement","canonical_anchor":"remote-control-minimum-version-enforcement","heading":"Remote Control Minimum Version Enforcement","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.53\/e\/remote-control-minimum-version-enforcement","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.53","markdown":"### Remote Control Minimum Version Enforcement\n\n**What**\n\nThe bridge (Remote Control) system now checks a server-specified minimum version requirement and blocks connections from outdated CLI versions.\n\n**Details**\n\n- On startup, the bridge checks the `tengu_bridge_min_version` feature flag for a required minimum version\n- If the running CLI version is too old, the user sees: \"Your version of Claude Code (X.X.X) is too old for Remote Control. Version Y.Y.Y or higher is required. Run `claude update` to update.\"\n- This applies to both standalone `claude bridge` mode and in-session REPL bridge connections\n\n**Evidence**\n\nVersion check using `tengu_bridge_min_version` flag (search for `\"tengu_bridge_min_version\"`)\n\n- Flag `tengu_bridge_min_version`: Not enough to say (read for one account on one subscription tier against v2.1.53; this account: no value returned, anonymous baseline: no value returned, compiled default: no gate table built for this version) 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."}