{"version":"2.1.293","anchor":"remote-control-errors-reported-after-a-session-moves-to-the","canonical_anchor":"remote-control-errors-reported-after-a-session-moves-to-the","heading":"Moving a session to the cloud now reports Remote Control problems separately","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/remote-control-errors-reported-after-a-session-moves-to-the","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Moving a session to the cloud now reports Remote Control problems separately\n\nIf a session moves to the cloud but Remote Control in your terminal fails to update, Claude Code reports it as a partial failure\n\n**What**\n\nRemote Control lets you reach a session running in your terminal from elsewhere. When you move a session to the cloud and the move succeeds but Claude Code did not finish updating Remote Control in this terminal, it now reports this as a partial failure. The message starts with \"Session now in the cloud:\" so you can see the move itself worked.\n\n**Why**\n\nA problem with the local Remote Control update no longer looks like the whole move failed. Your session is in the cloud even if this message appears.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}