What probably matters to youSection of the release
What
Directory sync, the mechanism that keeps a working directory tracked as it moves, normally anchors paths so it can follow a directory even if it is renamed. Setting CLAUDE_CODE_DIR_SYNC_DISABLE_ANCHORING turns that off and falls back to resolving paths by name, and the same release adds seven Claude-managed directory-sync variables to the set that is removed from the environment handed to child processes, so they do not leak into tools and subprocesses Claude Code spawns. Two of those seven names are reserved but do nothing yet.
Details
CLAUDE_CODE_DIR_SYNC_DISABLE_ANCHORING is unset by default and is recognised both as an environment variable and through the settings file; run it as CLAUDE_CODE_DIR_SYNC_DISABLE_ANCHORING=1 claude.
When anchoring is off by this variable, the reason is reported as switched_off.
Windows already skips anchoring regardless of the variable, and reports the reason platform.
CLAUDE_CODE_DIR_SYNC_ARCHIVE and CLAUDE_CODE_DIR_SYNC_OVERLAY are read nowhere in this build, so setting them has no effect; unlike their siblings they are absent from the typed environment accessor list and appear only in the filter set and the export map.
