{"version":"2.1.312","anchor":"remote-control-back-notice-records-how-long-a-peer-was-away","canonical_anchor":"remote-control-back-notice-records-how-long-a-peer-was-away","heading":"Remote control now records how long a peer was away","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/remote-control-back-notice-records-how-long-a-peer-was-away","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Remote control now records how long a peer was away\n\nThe notice that a peer is back in a remote-control session now records how long it was gone, alongside other session changes\n\n**What**\n\nRemote control lets you drive a Claude Code session from somewhere else. Several pieces of it changed:\n\n- The notice that a peer, meaning another connected party, is back now records both when it left and how long it was away, not only when it left.\n\n- A new type of progress message for a session's own row has been added.\n\n- A new kind of request the client can send to the running session has been added.\n\n- Sessions now keep the reason their last startup failed.\n\n**Why**\n\nThese are refinements to how remote and shared sessions show what is happening.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}