{"version":"2.1.310","anchor":"held-tool-results-flushed-when-store-needed","canonical_anchor":"held-tool-results-flushed-when-store-needed","heading":"Held tool results are sent on sooner when they need saving","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/held-tool-results-flushed-when-store-needed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Held tool results are sent on sooner when they need saving\n\nClaude Code now sends held-back tool results right away when one of them needs to be saved\n\n**What**\n\nA tool is an action Claude takes, such as reading a file, and its result is what came back. Claude Code holds some tool results back for a short time and then sends them on in a group. Previously it sent the group when a set time or number of events was reached, or after every call when set that way. It now also sends the group when a held result needs to be saved.\n\n**Why**\n\nThis changes when parts of the conversation record are uploaded, so results that need saving are not left waiting.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}