{"version":"2.1.290","anchor":"remote-control-state-parser-bridge-vs-legacy-engine-classi","canonical_anchor":"remote-control-state-parser-bridge-vs-legacy-engine-classi","heading":"Claude Code can now read two formats of remote-control state","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/remote-control-state-parser-bridge-vs-legacy-engine-classi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Claude Code can now read two formats of remote-control state\n\nClaude Code can now read a stored remote-control state in an older or newer format and sort it into one of several states\n\n**Unclear.** What uses this new reading, and whether it is switched on, is not clear.\n\n**What**\n\nClaude Code can now read a stored remote-control record in either of two formats: an older one that holds a state, or a newer one marked as using a \"bridge\". It sorts what it finds into one of these: none, unstated, unreadable, bridge, connected, requested, detached or other.\n\n**Why**\n\nThe stored remote-control state appears to now have more than one version.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}