{"version":"2.1.318","anchor":"remote-control-callout-flow-refactored-remote-control-dial","canonical_anchor":"remote-control-callout-flow-refactored-remote-control-dial","heading":"Remote Control dialog now says when it isn't connected","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/remote-control-callout-flow-refactored-remote-control-dial","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Remote Control dialog now says when it isn't connected\n\nThe `\/remote-control` dialog now shows when Remote Control isn't connected or needs a claude.ai sign-in, instead of assuming it is connected\n\n**What**\n\nRemote Control lets you reach a Claude Code session from claude.ai. The dialog opened by `\/remote-control` used to assume the session was connected. It can now show a problem state instead, with messages such as:\n\n- \"Remote Control isn't connected.\"\n\n- \"Remote Control needs a claude.ai sign-in.\"\n\nThe dialog also has a \"QR code unavailable\" option. The Disconnect item now explains that disconnecting can archive the session straight away and stop a later `--resume` from reconnecting it.\n\n**Why**\n\nIf your connection has dropped or you are not signed in, you now see why, instead of a message suggesting everything is connected.\n\n- Area: Remote Control\n- Names: `\/remote-control`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}