{"version":"2.1.277","anchor":"directory-sync-git-worker-gains-an-attached-machine-stan","canonical_anchor":"directory-sync-git-worker-gains-an-attached-machine-stan","heading":"Directory-sync git worker gains an 'attached machine' \/ standing-journal mode","tier":"internal","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/directory-sync-git-worker-gains-an-attached-machine-stan","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Directory-sync git worker gains an 'attached machine' \/ standing-journal mode\n\nDirectory sync's git worker gains an 'attached machine' mode with standing journals and new detach reasons\n\n**What**\n\nThe git-based directory-sync worker gained a substantial new code path around live syncing to a remote machine:\n\n- journals (its sync records) can now be \"standing\" as well as the previous \"note\"-based kind\n\n- checkouts can be \"attached\" to a live remote machine, tracked with a new `attached` flag and a `bookkeepingOnBranch` state\n\n- a new detach flow ends sync for specific reasons, such as `branch_switched` or `machine_stopped`, instead of only the previous generic \"ended\" flow\n\n- new fields `foldedInstall`, `readsStanding`, and a `keepCheckoutPath` marker (with a companion `.offered` file) track this state, letting an existing checkout be recognized as already attached instead of always redoing the initial setup\n\n**Why**\n\nThis lets directory sync track and recover a live connection to a remote machine more precisely, distinguishing why a sync session ended and avoiding unnecessary rework when a checkout is already properly set up.\n\n- Area: Directory Sync\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}