{"version":"2.1.283","anchor":"dir-sync-chained-pushes-are-now-always-on-claude-code-dir","canonical_anchor":"dir-sync-chained-pushes-are-now-always-on-claude-code-dir","heading":"Directory sync always sends changes as linked bundles, with no env var needed","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/dir-sync-chained-pushes-are-now-always-on-claude-code-dir","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Directory sync always sends changes as linked bundles, with no env var needed\n\nChained pushes in cloud directory sync are now always on, and `CLAUDE_CODE_DIR_SYNC_CHAIN` is no longer read\n\n**What**\n\nDirectory sync keeps your local folder and a cloud session's copy in step. Sending each turn's changes as a chain of linked bundles used to happen only when `CLAUDE_CODE_DIR_SYNC_CHAIN` was set to true. It is now always on, and that environment variable no longer appears in Claude Code at all.\n\nThe usage report Claude Code sends for each sync push has also changed: it no longer includes a \"held\" field, and it adds a field recording the cause when a snapshot is refused.\n\n**Why**\n\nBehaviour you previously had to opt into is now the default for every cloud file-sync session, so setting the variable no longer makes any difference.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}