{"version":"2.1.307","anchor":"answercallsneversent-distinguishes-calls-on-the-users-devic","canonical_anchor":"answercallsneversent-distinguishes-calls-on-the-users-devic","heading":"Calls that never reach your device get their own error message for Claude","tier":"notice","area":"Remote Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/answercallsneversent-distinguishes-calls-on-the-users-devic","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Calls that never reach your device get their own error message for Claude\n\nWhen a tool call on your own device was never sent, Claude now receives a fixed error message instead of one supplied by the host\n\n**What**\n\nA tool call is a request from Claude to run something, such as a command or a file read. When a tool call is never actually sent, Claude Code gives Claude a stand-in error result so the conversation can carry on.\n\nThat error now depends on where the call was meant to run. For calls on your own device, Claude Code uses a fixed message. Previously the message always came from the host, the program Claude Code is running inside.\n\n**Why**\n\nThis changes the wording Claude sees when such a call fails, which can affect how it explains or retries the failed step.\n\n- Area: Remote Tools\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}