Claude Code now quietly notes when a file you read has more than one name, without changing what's allowed.
tengu_playful_lobster Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.235: off
Read once, for one account on one subscription tier, against v2.1.235. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
When a file read is auto-allowed, Claude Code now quietly checks whether the target is a hardlink (more than one name pointing at the same file) and reports it. The permission decision is unchanged either way. The flag tengu_playful_lobster gates the reporting and falls back to on, so the measurement runs for everyone while no enforcement exists yet.
- The check stats the resolved path lazily and tests for a regular file with a link count above one.
- It fires
tengu_playful_lobster_firedwithstep(editImpliesReadorworkingDir), the permission mode, and a hardcodedmode: shadow. - Firing is deduped per mode and path, with a cap.
tengu_playful_lobster_fired
Strings lifted out of the shipped bundle, so the claim above can be checked against them.