{"version":"2.1.315","anchor":"server-side-clear-tool-uses-edits-now-get-a-client-side-clea","canonical_anchor":"server-side-clear-tool-uses-edits-now-get-a-client-side-clea","heading":"Claude Code now estimates and caps how much context the server reports clearing","tier":"notice","area":"Context Management","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/server-side-clear-tool-uses-edits-now-get-a-client-side-clea","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Claude Code now estimates and caps how much context the server reports clearing\n\nWhen the server clears old tool uses from context, Claude Code now estimates the tokens freed and caps the reported figure at that estimate\n\n**What**\n\nThe server can clear old tool uses from the conversation to free up room in the context. A tool use is one action Claude takes, such as reading a file or running a command. Until now, the number of input tokens freed this way came only from the server's own figure.\n\nClaude Code now makes its own estimate of the tokens freed by these clearings and records it with the result. The cleared total it reports is capped at that estimate. The summary shown when you come back after being idle now also counts how many tool uses were cleared while you were away.\n\n**Why**\n\nThis changes how much freed context Claude Code reports. The reported figure can now be lower than the server's number.\n\n- Area: Context Management\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}