{"version":"2.1.281","anchor":"directory-sync-claude-cloud-chained-link-bundles-nee","canonical_anchor":"directory-sync-claude-cloud-chained-link-bundles-nee","heading":"Directory sync (claude --cloud): chained 'link' bundles, need\/answer tracking and restoring an earlier environment","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/directory-sync-claude-cloud-chained-link-bundles-nee","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Directory sync (claude --cloud): chained 'link' bundles, need\/answer tracking and restoring an earlier environment\n\nCloud directory sync can now send each turn as a chained link and restore an earlier environment's work\n\n**What**\n\nWith `--cloud`, the part of directory sync that runs on the cloud side can now send each turn's changes as a new link in a chain, instead of overwriting one stored copy each time. A turn is one round of you sending a message and Claude answering. It also answers requests from your computer for the links it needs.\n\nIts saved state now keeps the chain of links and notes on inherited links, earlier environments, requests already answered, and whether linking has stopped. When a new cloud environment starts, it can rebuild an earlier environment's work from that chain and makes a commit saying \"claude --cloud directory sync: earlier environment restored\".\n\nThe `tengu_dir_sync_git_worker_armed` report gains `links_on_record`, `links_inherited` and `earlier_life`.\n\n**Why**\n\nWork from an earlier cloud environment can carry over into a new one instead of being lost, and past turns stay separate in the chain rather than being overwritten.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}