CLAUDE_CODE_DISABLE_DIR_SYNC
A Claude Code environment variable, read out of the shipped bundle. It was in the build from v2.1.229 and was gone by v2.1.285.
You can turn off background directory syncing by setting CLAUDE_CODE_DISABLE_DIR_SYNC.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.229.
In the changelogs
7Releases whose published page names CLAUDE_CODE_DISABLE_DIR_SYNC.
-
v2.1.285
Directory sync for cloud sessions and its environment variables removed
The directory-sync machinery for cloud sessions is gone, and its
CLAUDE_CODE_DIR_SYNC_*andCLAUDE_CODE_DISABLE_DIR_SYNCvariables no longer do anythingfound in this entry's text
-
v2.1.248
Directory sync loads a mid-turn hook from a separate build chunk
Directory sync loads an extra chunk to register a mid-turn hook, logging failures.
found in this entry's text
-
v2.1.239
Cloud file sync tracks deletions and tells you plainly when it recovers
Cloud file sync now tracks deletions and tells you plainly when it recovers.
found in this entry's text
-
v2.1.239
Directory-sync anchoring can be switched off, plus seven dir-sync variables now stripped from child processes
CLAUDE_CODE_DIR_SYNC_DISABLE_ANCHORING turns off path anchoring, and seven sync variables are now stripped from child processes.
found in this entry's text
-
v2.1.239
Sync and hook-forwarding switches now survive into remote sessions
Seven more environment variables you export locally now carry into remote and worker processes.
found in this entry's text
-
v2.1.238
Turns in cloud sessions now wait for a pre-turn check, which cannot yet refuse
Headless and SDK turns now wait on a pre-turn check that currently always says go ahead.
found in this entry's text
-
v2.1.229
Directory sync can be turned off with an environment variable
You can turn off background directory syncing by setting CLAUDE_CODE_DISABLE_DIR_SYNC.
named in this entry, found in this entry's text
First cited
0No release's published evidence quotes this name. The ledger indexes the Evidence lines of every changelog on this site, so this says nobody here has ever quoted it; it says nothing about how old the name is.
Presence across releases
2Build by build
68One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the environment variable does. All environment variables.