{"version":"2.1.292","anchor":"changed-file-check-resumes-where-it-left-off-after-an-abort","canonical_anchor":"changed-file-check-resumes-where-it-left-off-after-an-abort","heading":"Changed-file checks pick up where an interrupted check stopped","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/changed-file-check-resumes-where-it-left-off-after-an-abort","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Changed-file checks pick up where an interrupted check stopped\n\nIf Claude Code's check for changed files is interrupted, the next check now starts with the files it skipped instead of starting over\n\n**What**\n\nClaude Code keeps a list of files it has read during a session and checks them now and then to see whether they have changed on disk. Before, every check went through the whole list in the same order, and if a check was interrupted it lost its place.\n\nNow Claude Code remembers which files an interrupted check did not reach, and the next check starts with those. It also logs a warning saying how many of the tracked files were not examined.\n\n**Why**\n\nIn long sessions where turns are often interrupted, files near the end of the list could go unchecked again and again. Starting with the skipped files means every tracked file eventually gets looked at.\n\n- Flag `tengu_fallow_plover`: Off in both readings (read for one account on one subscription tier against v2.1.292; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}