{"version":"2.1.277","anchor":"new-two-copies-of-the-project-guidance-for-machinesession","canonical_anchor":"new-two-copies-of-the-project-guidance-for-machinesession","heading":"New \"two copies of the project\" guidance for machine\/session file-tool calls","tier":"internal","area":"Remote Machines","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/new-two-copies-of-the-project-guidance-for-machinesession","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### New \"two copies of the project\" guidance for machine\/session file-tool calls\n\nNew prompt guidance explains linked machines as separate, unsynced project copies with a commit-based workflow to move work between them\n\n**What**\n\nClaude Code's prompt now includes a large new block of guidance about working with a linked machine's copy of a project. It explains that:\n\n- The linked machine's folder is a separate copy of the project that is not automatically kept in sync\n\n- Tools like Read, Edit, Write, and Grep act on the current session's own checkout of the project\n\n- The same tools, when called against the linked machine, act on that machine's separate copy under that machine's own permission rules\n\n- A full git-based workflow is provided for moving work between the two copies, using commit IDs only\n\n- Branch or tag names should never be used for this, and `git pull` should never be used\n\n**Why**\n\nThis clears up a source of confusion when a session is linked to another machine: without it, Claude could easily assume both copies of a project are the same or automatically synced, and make edits in the wrong place or lose track of which copy has which changes. The commit-ID-only workflow gives a precise, unambiguous way to move work between the two.\n\n- Area: Remote Machines\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}