{"version":"2.1.318","anchor":"remote-control-device-report-carried-across-kill","canonical_anchor":"remote-control-device-report-carried-across-kill","heading":"Remote-control device report is kept when a session is stopped","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/remote-control-device-report-carried-across-kill","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Remote-control device report is kept when a session is stopped\n\nClaude Code now remembers whether a remote-control device report existed when a session was killed, so that state carries over\n\n**What**\n\nClaude Code now keeps track of whether a remote-control device report was present when a session was killed. It counts the report as carried over if it was recorded at the moment the session was stopped, or if a check for it reports one. This works the same way as an existing carry-over for other leftover items from a stopped session.\n\n**Why**\n\nThis is part of how Claude Code tracks state for remote control, the feature that lets a session be driven from another device. It is not clear that it changes anything you see.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}