{"version":"2.1.224","anchor":"remote-control-disconnects-appear-in-the-transcript","canonical_anchor":"remote-control-disconnects-appear-in-the-transcript","heading":"Remote Control disconnects appear in the transcript","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/remote-control-disconnects-appear-in-the-transcript","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Remote Control disconnects appear in the transcript\n\nLosing Remote Control now adds a transcript warning hinting at `\/remote-control` to reconnect.\n\n**What**\n\nLosing the Remote Control connection now adds a warning message to the conversation instead of failing silently, with a hint to run `\/remote-control` to reconnect. The hint is omitted when the reason already mentions logging in, remote control, a restart, policy or an update, and an identical message is not repeated twice in a row.\n\n**Details**\n\n- only reached while the Remote Control bridge is running\n- errors now also record whether the cause was the terminal or something else\n\n**Evidence**\n\n` \\u2014 run \/remote-control to reconnect`\n\n- Area: Remote Control\n- Names: `\/remote-control`, `\/remote`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}