{"version":"2.1.314","anchor":"remote-sessions-track-foreground-tasks","canonical_anchor":"remote-sessions-track-foreground-tasks","heading":"Remote sessions keep track of foreground tasks","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/remote-sessions-track-foreground-tasks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Remote sessions keep track of foreground tasks\n\nRemote sessions now keep a list of foreground tasks alongside background ones, and a new instruction tells Claude to wait for results it needs\n\n**Unclear.** What decides whether the new instruction to wait for results is used is not shown.\n\n**What**\n\nA remote session is a Claude Code session that runs on another machine. Remote sessions already kept a list of background tasks, which are tasks that keep running while the conversation goes on. They now also keep a list of foreground tasks. The list is filled when the session starts, updated each time a task reports a result, and cleared when the worker running the session is reported gone.\n\nSome other changes come with it:\n\n- A new event marks a reply as held.\n\n- The record of a finished reply is reset at the start of each turn.\n\n- A new version of Claude's instructions tells it to wait in the foreground for a result it needs before replying. A check decides when this version is used.\n\n**Why**\n\nThis changes how Claude is told to handle results from tasks it has started.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}