{"version":"2.1.318","anchor":"bridge-session-stand-in-and-a-refusal-wait-parameter","canonical_anchor":"bridge-session-stand-in-and-a-refusal-wait-parameter","heading":"Remote Control groundwork for a stand-in program when the original is removed","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/bridge-session-stand-in-and-a-refusal-wait-parameter","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Remote Control groundwork for a stand-in program when the original is removed\n\nNew, not yet connected code lets Remote Control find a replacement Claude Code program if the one it started from was removed by an update\n\n**What**\n\nRemote Control lets you drive a Claude Code session from another device. New code covers the case where the Claude Code program file that Remote Control started from has since been deleted, for example by an update.\n\n- It looks for a replacement program, either the native install or a Homebrew install, and records a `bridge_session_stand_in` error kind.\n\n- It warns: \"The program file this Remote Control started from is gone, most likely removed by an update.\"\n\n- Related additions: a `refusalWaitMs` setting on one component, and session state fields `moveFirstTurn`, `moveSends` and `sentBeforeStop`, which look like groundwork for moving a Remote Control session.\n\nNo caller for any of this was confirmed, so it may not run yet.\n\n**Why**\n\nIf this is connected, Remote Control would be able to keep starting new sessions after Claude Code updates itself in place, rather than failing because its original program file disappeared. For now it is groundwork.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}