{"version":"2.1.282","anchor":"settings-review-store-refuses-hard-linked-settings-files","canonical_anchor":"settings-review-store-refuses-hard-linked-settings-files","heading":"Accepting a settings proposal no longer writes through a hard-linked file","tier":"notice","area":"Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/settings-review-store-refuses-hard-linked-settings-files","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Accepting a settings proposal no longer writes through a hard-linked file\n\nClaude Code now refuses to accept a proposed settings change in place when the settings file is hard-linked to another file\n\n**Unclear.** What Claude Code shows you when an accept is refused as `hard_linked` is not known.\n\n**What**\n\nWhen you accept a proposed change to a settings file, Claude Code sometimes writes the new content directly into the existing file. It now checks first whether that file is hard-linked. A hard link is a second name for the same file on disk, so writing through one name also changes the file under the other name.\n\nIf the settings file is hard-linked, Claude Code does not write to it and reports the outcome as `hard_linked` instead.\n\n**Why**\n\nThis closes a way for accepting a settings change to quietly modify some other file on your disk that happens to share the same data through a hard link.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}