{"version":"2.1.323","anchor":"tool-result-clearing-estimates-handle-images-and-client-side","canonical_anchor":"tool-result-clearing-estimates-handle-images-and-client-side","heading":"Better estimates of space freed when old tool output is cleared","tier":"internal","area":"Context Management","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/tool-result-clearing-estimates-handle-images-and-client-side","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Better estimates of space freed when old tool output is cleared\n\nEstimates of space freed by clearing old tool output now count images by size and can include cleared tool inputs\n\n**What**\n\nTo keep a long conversation within Claude's limits, Claude Code can clear out old tool results, the output from actions Claude took. It estimates how much space this frees, measured in tokens, the small pieces of text Claude reads. The estimate changed:\n\n- Images are now counted by their size instead of at a flat cost each.\n\n- Tool inputs can now be cleared for specific named tools.\n\n- Tool calls cut by Claude Code itself are now counted.\n\nUsage reporting now also says whether a figure was measured, estimated by Claude Code, or supplied by the server.\n\n**Why**\n\nThis changes how Claude Code accounts for the space freed when old tool output is cleared.\n\n- Area: Context Management\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}