Under the hood
New prompt guidance explains linked machines as separate, unsynced project copies with a commit-based workflow to move work between them
What
Claude 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:
- The linked machine's folder is a separate copy of the project that is not automatically kept in sync
- Tools like Read, Edit, Write, and Grep act on the current session's own checkout of the project
- The same tools, when called against the linked machine, act on that machine's separate copy under that machine's own permission rules
- A full git-based workflow is provided for moving work between the two copies, using commit IDs only
- Branch or tag names should never be used for this, and
git pullshould never be used
Why
This 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.