{"version":"2.1.292","anchor":"remote-sessions-record-programs-a-command-left-running-and-t","canonical_anchor":"remote-sessions-record-programs-a-command-left-running-and-t","heading":"Restored remote sessions can tell Claude which background programs stopped","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/remote-sessions-record-programs-a-command-left-running-and-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Restored remote sessions can tell Claude which background programs stopped\n\nRemote sessions can record programs a command left running and, on restore, tell Claude which ones are no longer running\n\n**What**\n\nIn remote sessions, Claude Code can now note the background programs a command left running, such as a development server started by a shell command. When the session is later restored, it checks whether those programs are still running. For any that have gone, it adds a note for Claude saying that programs left running by those earlier commands are not running on this machine now.\n\nRecording these programs sits behind a server-controlled switch that is off unless it is switched on remotely.\n\n**Why**\n\nA cloud or remote session that restarts will no longer have Claude assume that a server it started earlier is still up, which avoids confusing errors when it tries to use it.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}