{"version":"2.1.232","anchor":"remote-control-refuses-to-attach-when-a-local-process-holds-","canonical_anchor":"remote-control-refuses-to-attach-when-a-local-process-holds-","heading":"Remote Control refuses to attach when a local process holds the session","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/remote-control-refuses-to-attach-when-a-local-process-holds-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Remote Control refuses to attach when a local process holds the session\n\nRemote Control declines to attach when a local process holds the session and tells you in the transcript.\n\n**What**\n\nWhen the Remote Control bridge starts and finds a local process already holding the session, it logs the decline, posts a one-time informational notice into the transcript, and switches the bridge off for that session instead of connecting.\n\n**Details**\n\n- Both the bridge enable flag and its auto-on default are cleared when this happens.\n- The attach path can now carry a session to reattach to and a flag to keep the session on exit, tracked internally as never-archive, and identity changes are reported to the bridge state machine.\n- Whether the surrounding bridge feature is on by default is not decided in this code; it only runs inside Remote Control sessions.\n\n**Evidence**\n\n`[bridge:repl] Init declined: session held by local pid `\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}