{"version":"2.1.286","anchor":"redrive-tracking-replaces-consume-in-the-lag-probe","canonical_anchor":"redrive-tracking-replaces-consume-in-the-lag-probe","heading":"Internal responsiveness check records when and why work is repeated","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/redrive-tracking-replaces-consume-in-the-lag-probe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Internal responsiveness check records when and why work is repeated\n\nClaude Code's internal lag check now records when work was first sent and what caused it to be sent again\n\n**Unclear.** It is unclear whether any of this is visible to you.\n\n**What**\n\nClaude Code has an internal check that watches for lag and resource use. It now records when a piece of work was first sent off and what caused it to be sent again, instead of simply marking the work as used.\n\n**Why**\n\nThis is diagnostic information about why the screen is redrawn.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}