{"version":"2.1.319","anchor":"remote-tool-call-approval-edited-input-is-no-longer-applied","canonical_anchor":"remote-tool-call-approval-edited-input-is-no-longer-applied","heading":"Edited approvals no longer change a remote tool call's input","tier":"notice","area":"Sessions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/remote-tool-call-approval-edited-input-is-no-longer-applied","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Edited approvals no longer change a remote tool call's input\n\nIf approving a remote tool call comes back with edited input, Claude Code now refuses the call instead of running the edited version\n\n**What**\n\nA tool call is one action Claude takes, such as running a command or editing a file. Some tool calls are carried out on a remote host, which is another machine, and they need approval first.\n\nSometimes the approval answer for a remote call comes back with changed input. Claude Code used to check the changed version and send it on. It now ends the call with an error and records the approval as edited.\n\nThe approval check can also compare the permitted input with the original, to see whether it is still the same call.\n\n**Why**\n\nAnswering an approval prompt can no longer quietly rewrite what a remote host is asked to do. The remote host runs the call as it was asked for, or it does not run it at all.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}