{"version":"2.1.309","anchor":"served-policy-turn-hold-can-start-in-each-call-mode","canonical_anchor":"served-policy-turn-hold-can-start-in-each-call-mode","heading":"Remote sessions can hold the first turn's uploads one tool call at a time","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/served-policy-turn-hold-can-start-in-each-call-mode","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Remote sessions can hold the first turn's uploads one tool call at a time\n\nIf the server's upload policy asks for it, a remote session's first turn holds uploads per tool call instead of for the whole turn\n\n**What**\n\nIn a remote session, Claude Code runs on a server and uploads what happens as it goes, sometimes holding uploads back for a while. When the server's upload policy turns on the per-call option and Claude's turn has not ended yet, the first hold of a turn now applies to each tool call (each action Claude takes) separately. Before, it always held the whole turn.\n\n**Why**\n\nIt changes how quickly tool-call activity reaches the server at the start of a turn in remote sessions. The server decides whether this applies.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}