{"version":"2.1.314","anchor":"editwrite-run-an-extra-permission-check-and-hide-staged-con","canonical_anchor":"editwrite-run-an-extra-permission-check-and-hide-staged-con","heading":"Staged edits from another machine no longer include file contents","tier":"notice","area":"File Edits","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/editwrite-run-an-extra-permission-check-and-hide-staged-con","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Staged edits from another machine no longer include file contents\n\nEdit and Write now run an extra path check and leave file contents and diffs out of staged results for calls from another machine\n\n**Unclear.** Which paths or permissions the new check refuses is not stated.\n\n**What**\n\nEdit and Write are the tools Claude uses to change and create files. An edit can be staged for review, meaning it is held for you to approve rather than applied straight away.\n\n- When a staged Edit or Write came from a remote call or from another machine, the result no longer includes the file's contents or the diff (the list of changed lines). `originalFile` is null, `structuredPatch` is empty, and `oldString`\/`newString` are taken from the raw request.\n\n- A staged Write from your own machine now gets a real diff, where before it was always empty. The diff is still left out when the call is remote, the file does not exist, or the file is large.\n\n- Edit and Write both run a new check on the file path and permissions before working, and stop with that check's message if it refuses.\n\n**Why**\n\nFile contents are no longer sent back in staged-review results for calls from another machine, local staged writes now show what they would change, and some paths may now be refused.\n\n- Area: File Edits\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}