{"version":"2.1.300","anchor":"read-before-edit-touch-comparison-reports-an-outcome-and-all","canonical_anchor":"read-before-edit-touch-comparison-reports-an-outcome-and-all","heading":"File change check before edits now records why it gave up, and accepts a linked outputs folder","tier":"internal","area":"File Editing","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/read-before-edit-touch-comparison-reports-an-outcome-and-all","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### File change check before edits now records why it gave up, and accepts a linked outputs folder\n\nClaude Code's check on whether a file changed since it was read now records a reason, and accepts an outputs path that is a link when one is set\n\n**What**\n\nBefore editing a file, Claude Code compares it with the copy it read earlier to see whether it has changed. That comparison used to give only a yes or no. It now records which outcome it reached:\n\n- `partial_view`: only part of the file had been read\n\n- `enoent`: the file does not exist\n\n- `nlink`: the file has more than one hard link (more than one name pointing at the same data)\n\n- `link_on_path`: there is a link somewhere in the file's path\n\n- `same`: the file is unchanged\n\n- `differs`: the file has changed\n\nIt also now accepts an outputs path that is a symbolic link (a shortcut to another folder) when such a path is configured.\n\n**Why**\n\nMost of this only helps Claude Code report what happened. The one change in behavior is that a configured outputs folder reached through a link no longer stops the comparison.\n\n- Area: File Editing\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}