{"version":"2.1.281","anchor":"remote-tool-calls-refuse-path-spellings-the-sessions-rules","canonical_anchor":"remote-tool-calls-refuse-path-spellings-the-sessions-rules","heading":"Remote tool calls refuse path spellings the session's rules cannot match","tier":"notice","area":"Remote Devices","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/remote-tool-calls-refuse-path-spellings-the-sessions-rules","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Remote tool calls refuse path spellings the session's rules cannot match\n\nRemote tool calls are refused with declined_spelling when a path is written in a form the session's path rules cannot match\n\n**What**\n\nWhen Claude Code sends a tool call to another computer (a remote host), it first checks the call against your permission rules, including rules about which file paths are allowed. It now also checks alternative ways of writing the same path. If a path is written in a form your session's path rules cannot match, the call is refused with the code `declined_spelling` and the remote host is never contacted. The model is told to use the file's full path as the tool shows it.\n\nThe path filling-in that used to apply only to a `file_path` field now applies to whichever field holds the path for any tool. The permission check runs over the original input, the alternative spellings and the rewritten input, and stops at the first refusal.\n\n**Why**\n\nA path rule only protects you if it can recognise the path. Writing a path in an unusual way could otherwise let a call reach a remote machine without your rules ever applying to it.\n\n- Area: Remote Devices\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}