{"version":"2.1.293","anchor":"idle-retry-check-refactored","canonical_anchor":"idle-retry-check-refactored","heading":"The check for retrying after idle time now uses a shared helper","tier":"internal","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/idle-retry-check-refactored","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### The check for retrying after idle time now uses a shared helper\n\nClaude Code's check for when to retry after a period of idle time has been rewritten to use a single shared helper\n\n**Unclear.** Whether the timing of the idle retry actually changed or the rewrite keeps it the same.\n\n**What**\n\nClaude Code has a check that decides when to retry something after a period of idle time. That check used to compare the current time against the later of two recorded times, plus one extra condition. It now hands the whole decision to a single shared helper.\n\n**Why**\n\nThe rewrite may change when the idle or retry timer fires. If you notice a retry happening sooner or later than before, this is a likely place to look.\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}