{"version":"2.1.277","anchor":"multi-machine-sessions-now-distinguish-a-separate-synced-che","canonical_anchor":"multi-machine-sessions-now-distinguish-a-separate-synced-che","heading":"Multi-machine sessions now distinguish a separate synced checkout from the primary one","tier":"notice","area":"Remote Machines","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/multi-machine-sessions-now-distinguish-a-separate-synced-che","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Multi-machine sessions now distinguish a separate synced checkout from the primary one\n\nMulti-machine session messages now distinguish a synced mirror from a separate, unsynced copy\n\n**What**\n\nWhen a session shows which machines are attached to it, Claude Code now handles a new case: the current session's checkout being the primary copy of the project, while a named machine holds the user's own separate copy with nothing synced between the two. This gets its own explanatory text, distinct from the existing case where a machine holds a synced mirror of the project.\n\n**Why**\n\nThis makes it clearer when working across multiple machines whether changes on one machine will show up on another, avoiding confusion about whether two checkouts are actually kept in sync.\n\n- Area: Remote Machines\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}