{"version":"2.1.225","anchor":"bridge-reattach-can-fail-hard-instead-of-silently-starting-a","canonical_anchor":"bridge-reattach-can-fail-hard-instead-of-silently-starting-a","heading":"Bridge reattach can fail hard instead of silently starting a new session","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/bridge-reattach-can-fail-hard-instead-of-silently-starting-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Bridge reattach can fail hard instead of silently starting a new session\n\nAfter re-authenticating, Remote Control reattaches to your existing session or says it's gone, instead of quietly starting a new one.\n\n**What**\n\nAn auth-triggered revive now either reattaches to the same session or reports a dead pointer, rather than quietly creating a fresh session under the old one.\n\n**Details**\n\n- REPL bridge session options gained `reattachOrFail`, `reviveInitiated`, `onAuthProven` and `onReattachPointerDead`.\n- The caller passes `reattachOrFail` only when a revive was initiated and a previous session id is known.\n\n**Evidence**\n\n`onReattachPointerDead`\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}