Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Remote MachinesArea: what it touches
Internal ChangesKind: in v2.1.277,
Internal ChangesSection of the release
What
Claude Code now includes detailed built-in instructions for situations where a remote or bridged machine's project folder is a separate copy of the repository that isn't kept in sync with the current session's checkout. The guidance covers:
File tools only act on the current session's own checkout, not the remote copy
Moving work between the two copies must go through git fetch, rev-parse, and reviewing the commit ID
Warnings about risks from hooks, submodules, .gitattributes, .lfsconfig, and Git LFS (Git's large file storage extension) when working across separate copies
This is wired in as a new "separate" case alongside existing handling for other machine-relationship states.
Why
This reduces the risk of Claude Code confusing two unsynced copies of a project when operating across a remote or bridged machine, and steers it toward safe, reviewable ways to move changes between them.
