{"version":"2.1.318","anchor":"clear-tool-uses-edit-accounts-for-tool-uses-since-idle-retur","canonical_anchor":"clear-tool-uses-edit-accounts-for-tool-uses-since-idle-retur","heading":"Clearing old tool results now counts tool calls made after you return from idle","tier":"internal","area":"Context Management","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/clear-tool-uses-edit-accounts-for-tool-uses-since-idle-retur","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Clearing old tool results now counts tool calls made after you return from idle\n\nWhen old tool results are trimmed from context, the thresholds now add tool calls made since you came back from being idle\n\n**Unclear.** It is not clear what decides whether the after-idle path is used.\n\n**What**\n\nClaude Code can ask for old tool results to be cleared from the conversation's context, the text Claude reads each turn, to save space. The point at which clearing starts, and how many results it keeps, now add the number of tool calls made since you returned after being idle. Before, these used fixed base values.\n\nClaude Code also has a new way to estimate how many tokens were cleared, measured from the prompts themselves. Tokens are the units text is counted in.\n\n**Why**\n\nThis changes when tool results get cleared after you step away and come back.\n\n- Area: Context Management\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}