What
When 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.
If the settings file is hard-linked, Claude Code does not write to it and reports the outcome as hard_linked instead.
Why
This 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.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What Claude Code shows you when an accept is refused as `hard_linked` is not known.