{"version":"2.1.284","anchor":"new-profiling-checkpoints-for-idle-tool-result-clearing-and","canonical_anchor":"new-profiling-checkpoints-for-idle-tool-result-clearing-and","heading":"New timing checkpoints for idle tool-result clearing and computer-use summaries","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/new-profiling-checkpoints-for-idle-tool-result-clearing-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### New timing checkpoints for idle tool-result clearing and computer-use summaries\n\nClaude Code now records timing checkpoints when idle-time tool-result clearing starts and when a computer-use action is first summarised\n\n**Unclear.** What controls whether those two features themselves are switched on is not known.\n\n**What**\n\nClaude Code has two new internal timing checkpoints, markers it records to measure performance:\n\n- One when clearing of old tool results after the session sits idle is switched on. A tool result is the output Claude gets back from an action such as running a command. Failures of that clearing are logged under the same name.\n\n- One the first time an action taken by computer use (Claude operating a desktop) is summarised.\n\n**Why**\n\nThese markers point to two features being measured: clearing tool results after a session sits idle, and summarising computer-use actions.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}