{"version":"2.1.281","anchor":"dir-sync-windows-anchoring-via-a-win32-handle-backend","canonical_anchor":"dir-sync-windows-anchoring-via-a-win32-handle-backend","heading":"dir-sync: Windows anchoring via a win32 handle backend","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/dir-sync-windows-anchoring-via-a-win32-handle-backend","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### dir-sync: Windows anchoring via a win32 handle backend\n\nOn Windows, dir-sync can now anchor its root folder through a native Windows handle, with fallbacks when that is not possible\n\n**Unclear.** The finding does not say what anchoring protects against or what the fallback modes mean for syncing.\n\n**What**\n\nOn Windows, dir-sync, Claude Code's folder syncing, now anchors its root folder through a `win32_handle` backend. To do this it loads an NT FFI, a way of calling Windows system functions directly. If this does not work, the anchoring either falls back to `no_ffi` or goes without anchoring and records a reason why.\n\nThe `CLAUDE_CODE_DIR_SYNC_DISABLE_ANCHORING` environment variable is checked before any of this happens.\n\n**Why**\n\nWindows machines now take part in dir-sync root anchoring. `CLAUDE_CODE_DIR_SYNC_DISABLE_ANCHORING` is the setting to look at if you need to keep anchoring out of the way."}