{"version":"2.1.288","anchor":"changed-file-attachment-skips-re-reads-behind-tengu-fallow-p","canonical_anchor":"changed-file-attachment-skips-re-reads-behind-tengu-fallow-p","heading":"Claude Code may skip re-reading files that only look changed","tier":"soon","area":"File Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/changed-file-attachment-skips-re-reads-behind-tengu-fallow-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Claude Code may skip re-reading files that only look changed\n\nA new check can skip re-reading a file Claude has seen when its timestamp is newer, and the number actually re-read is recorded\n\n**Unclear.** It is not clear what the new check compares before skipping a file.\n\n**What**\n\nWhen a file Claude has already read changes on disk, Claude Code re-reads it and tells Claude what changed. Until now, every file with a newer modification time was re-read and compared. A new check now runs first, and if it passes, the file is skipped. Claude Code also records how many files were actually re-read. This sits behind the tengu_fallow_plover gate, a switch Anthropic controls remotely.\n\n**Why**\n\nThis is likely to cut needless file reads and change notices when a file's timestamp moves but its contents do not.\n\n- Flag `tengu_fallow_plover`: Not enough to say (read for one account on one subscription tier against v2.1.288; this account: no value returned, anonymous baseline: no value returned, 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: File Tools\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}