{"version":"2.1.310","anchor":"transportccr-heartbeat-and-held-result-state-added","canonical_anchor":"transportccr-heartbeat-and-held-result-state-added","heading":"Remote sessions gain tracking for tool results that are held back","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/transportccr-heartbeat-and-held-result-state-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Remote sessions gain tracking for tool results that are held back\n\nThe client for remote sessions now keeps track of tool results that are being held back within a turn\n\n**Unclear.** Whether remote sessions actually hold any tool results back yet is not shown.\n\n**What**\n\nIn a remote session, which is a Claude Code session running on another machine such as in the cloud, the part of Claude Code that talks to that machine now keeps track of tool results that are waiting to be delivered. A tool result is the output Claude gets back after it uses a tool, such as running a command. It also tracks which calls have results waiting and whether a held result still needs to be saved.\n\n**Why**\n\nThis lays the ground for remote sessions to hold some tool results back across a turn instead of delivering each one immediately.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}