{"version":"2.1.277","anchor":"extensive-new-prompt-guidance-for-tool-calls-against-a-sepa","canonical_anchor":"extensive-new-prompt-guidance-for-tool-calls-against-a-sepa","heading":"Extensive new prompt guidance for tool calls against a 'separate' (unsynced) machine copy","tier":"internal","area":"Remote Machines","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/extensive-new-prompt-guidance-for-tool-calls-against-a-sepa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Extensive new prompt guidance for tool calls against a 'separate' (unsynced) machine copy\n\nNew built-in guidance tells Claude how to safely handle tool calls against a separate, unsynced copy of a project on a remote machine\n\n**What**\n\nClaude 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:\n\n- File tools only act on the current session's own checkout, not the remote copy\n\n- Moving work between the two copies must go through `git fetch`, `rev-parse`, and reviewing the commit ID\n\n- Warnings about risks from hooks, submodules, `.gitattributes`, `.lfsconfig`, and Git LFS (Git's large file storage extension) when working across separate copies\n\nThis is wired in as a new \"separate\" case alongside existing handling for other machine-relationship states.\n\n**Why**\n\nThis 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.\n\n- Area: Remote Machines\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}