{"version":"2.1.317","anchor":"file-change-reminders-carry-re-read-entry-unchanged-file-re","canonical_anchor":"file-change-reminders-carry-re-read-entry-unchanged-file-re","heading":"Read no longer answers a repeat read with a 'file unchanged' result","tier":"notice","area":"File Tools","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/file-change-reminders-carry-re-read-entry-unchanged-file-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Read no longer answers a repeat read with a 'file unchanged' result\n\nThe Read tool's `file_unchanged` result, a short reply for files not changed since the last read, is removed; edited-file reminders gain `rereadEntry`\n\n**What**\n\nRead is the tool Claude uses to open files. It used to have a shortcut: if Claude read a file again and it had not changed since the last read, Read could send back a short `file_unchanged` result instead of the file's content. That shortcut has been removed:\n\n- The code in Read that produced `file_unchanged` is deleted. It was guarded by the `tengu_read_dedup_killswitch` flag and a `dedupUnchangedReads` setting; this code no longer reads the flag, and whether anything else still reads it was not checked.\n\n- The `dedupUnchangedReads` setting is gone from the tool's context, including a place that set it to false.\n\n- Read's output description no longer includes the `file_unchanged` type or its `seeded` source, which marked a match against something loaded at startup, such as CLAUDE.md or nested memory files, rather than an earlier Read.\n\n- The way a `file_unchanged` result was turned into a message for Claude is removed too.\n\n- Reminders that tell Claude a text file was edited now carry a `rereadEntry` (a hash and a length) when the file had been read in full.\n\nThe stock description of the Read tool, captured under this release, is unchanged.\n\n**Why**\n\nIn this code, a repeat read of an unchanged file no longer gets the short stub. Whether unchanged re-reads are now handled somewhere else, for example through the new `rereadEntry`, is not shown, so how much of the conversation repeat reads take up may differ.\n\n- Area: File Tools\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}