Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

CLAUDE_CODE_DIR_SYNC_CHAIN

env gone JSON

A Claude Code environment variable, read out of the shipped bundle. It was in the build from v2.1.280 and was gone by v2.1.283.

A new 'chained' directory-sync mode exists behind an undocumented CLAUDE_CODE_DIR_SYNC_CHAIN env var

Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.280.

First seen v2.1.280 22 Sep 2026
Last seen v2.1.282 24 Sep 2026, gone by v2.1.283
Builds3 / 126on this box, as of v2.1.283
Written about v2.1.280 first named in a changelog, 22 Sep 2026
v2.1.280in the build not in the build never minedv2.1.283

In the changelogs

4

Releases whose published page names CLAUDE_CODE_DIR_SYNC_CHAIN.

  1. v2.1.283
    Directory sync always sends changes as linked bundles, with no env var needed

    Chained pushes in cloud directory sync are now always on, and CLAUDE_CODE_DIR_SYNC_CHAIN is no longer read

    found in this entry's text

  2. v2.1.281
    Directory sync link-chain shipping on the cloud worker depends on a laptop env var

    --cloud directory sync can send each turn's changes as linked bundles, but only when the laptop sets CLAUDE_CODE_DIR_SYNC_CHAIN

    found in this entry's text

  3. v2.1.280
    A 'chained' directory-sync mode exists, gated by an undocumented env var

    A new 'chained' directory-sync mode exists behind an undocumented CLAUDE_CODE_DIR_SYNC_CHAIN env var

    found in this entry's text, named in this entry

  4. v2.1.280
    Windows-specific env vars added to the host-passthrough allowlist

    More environment variables, including Windows-specific ones, now pass through to Claude Code

    found in this entry's text

First cited

2

The earliest release whose published evidence quoted CLAUDE_CODE_DIR_SYNC_CHAIN was v2.1.280, 22 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

ReleaseDateThe span that was quoted
v2.1.28022 Sep 2026a.CLAUDE_CODE_DIR_SYNC_CHAIN === !0
v2.1.28325 Sep 2026CLAUDE_CODE_DIR_SYNC_CHAIN

Presence across releases

2
BuildsHow manyDatesReading
v2.1.280 – v2.1.2823 builds22 Sep 2026 → 24 Sep 2026 ◆in the build
v2.1.2831 build25 Sep 2026 ○not in the build

Build by build

4

One 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.

BuildDateStateThe record behind it
v2.1.28022 Sep 2026·addedverdict: added · bool
v2.1.28123 Sep 2026·presentverdict: present · bool
v2.1.28224 Sep 2026·presentverdict: present · bool
v2.1.28325 Sep 2026·removedverdict: removed

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.

Feedback