{"version":"2.1.311","anchor":"tool-call-hold-can-start-on-the-second-call-when-a-later-wor","canonical_anchor":"tool-call-hold-can-start-on-the-second-call-when-a-later-wor","heading":"Remote sessions can start holding events from the second tool call","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/tool-call-hold-can-start-on-the-second-call-when-a-later-wor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Remote sessions can start holding events from the second tool call\n\nIn remote and worker sessions, Claude Code can now start holding back events from the second tool call instead of the first\n\n**Unclear.** What this changes for someone using a remote session is not clear.\n\n**What**\n\nIn remote and worker sessions, Claude Code sometimes holds back events before sending them on. A remote session is one that runs somewhere other than your own terminal. A tool call is a single action Claude takes, such as running a command.\n\nThere is a new rule for when that hold begins. When a later worker is holding the first turn, the hold now starts on the second tool call. When the session closes, Claude Code also stops a new keep-alive signal that runs while work is starting.\n\n**Why**\n\nThis affects when remote and worker sessions send their events on.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}