{"version":"2.1.281","anchor":"directory-sync-link-chain-shipping-on-the-cloud-worker-depen","canonical_anchor":"directory-sync-link-chain-shipping-on-the-cloud-worker-depen","heading":"Directory sync link-chain shipping on the cloud worker depends on a laptop env var","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/directory-sync-link-chain-shipping-on-the-cloud-worker-depen","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Directory sync link-chain shipping on the cloud worker depends on a laptop env var\n\n`--cloud` directory sync can send each turn's changes as linked bundles, but only when the laptop sets `CLAUDE_CODE_DIR_SYNC_CHAIN`\n\n**What**\n\nWhen you use `--cloud`, directory sync keeps your local folder and the cloud session's copy in step. The cloud side is called the worker, and your machine is called the laptop.\n\nThere is a new way to send changes. The laptop can offer a word, `appliesLinks`, in the note it sends to the worker. When the worker sees it, and the laptop accepts held parents, the worker does three new things:\n\n- sends each turn's changes as a chain of linked bundles instead of the usual outbound path\n\n- records those links in its saved state, so it can restore an earlier environment after it is recreated and log \"claude --cloud directory sync: earlier environment restored\"\n\n- reports new telemetry (usage data) fields `links_on_record`, `links_inherited` and `earlier_life`\n\nThe laptop only offers `appliesLinks` when the environment variable `CLAUDE_CODE_DIR_SYNC_CHAIN` is set. An environment variable is a named setting passed to a program when it starts. Without it, the worker behaves as before and logs nothing new.\n\n**Why**\n\nBy default nothing changes. With `CLAUDE_CODE_DIR_SYNC_CHAIN` set on your machine, a cloud session can carry its synced history across being recreated."}