{"version":"2.1.225","anchor":"remote-control-refuses-to-mint-a-fresh-session-when-reattach","canonical_anchor":"remote-control-refuses-to-mint-a-fresh-session-when-reattach","heading":"Remote Control refuses to mint a fresh session when reattach is required","tier":"soon","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/remote-control-refuses-to-mint-a-fresh-session-when-reattach","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Remote Control refuses to mint a fresh session when reattach is required\n\nRemote Control can now fail loudly instead of silently starting a new session when it can't reattach.\n\n**What**\n\nWhen init runs in reattach-or-fail mode, a reattach pointer that is gone (or absent entirely) now fails terminally with a user-facing message instead of quietly creating a new remote session.\n\n**Details**\n\n- Covers both the gone-pointer case and the no-pointer-at-all case.\n- Emits distinct telemetry for each failure shape.\n- The enabled state of the reattach-or-fail mode itself could not be resolved from the build.\n\n**Evidence**\n\n`[remote-bridge] Reattach-or-fail: no reattach pointer for this init; failing terminally instead of minting fresh`\n\n- Area: Remote Control\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}