{"version":"2.1.280","anchor":"a-chained-directory-sync-mode-exists-gated-by-an-undocume","canonical_anchor":"a-chained-directory-sync-mode-exists-gated-by-an-undocume","heading":"A 'chained' directory-sync mode exists, gated by an undocumented env var","tier":"use","area":"Directory Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/a-chained-directory-sync-mode-exists-gated-by-an-undocume","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### A 'chained' directory-sync mode exists, gated by an undocumented env var\n\nA new 'chained' directory-sync mode exists behind an undocumented CLAUDE_CODE_DIR_SYNC_CHAIN env var\n\n**Unclear.** The finding does not say what directory-sync 'chained' mode actually does differently, or who it is intended for.\n\n**What**\n\nThe engine that keeps directories in sync now has a `chained` mode. It stays off unless an environment variable called `CLAUDE_CODE_DIR_SYNC_CHAIN` is set to exactly `true`.\n\n**Why**\n\nSince this isn't documented and requires manually setting an environment variable, most users won't encounter it. It appears to be an internal or experimental switch rather than a supported option.\n\n- Area: Directory Sync\n- Names: `CLAUDE_CODE_DIR_SYNC_CHAIN`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}