{"version":"2.1.281","anchor":"remote-tool-calls-standing-requests-can-be-inherited-and-wi","canonical_anchor":"remote-tool-calls-standing-requests-can-be-inherited-and-wi","heading":"Remote tool calls: standing requests can be inherited and withdrawn on interrupt; 'still running' corrections","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/remote-tool-calls-standing-requests-can-be-inherited-and-wi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Remote tool calls: standing requests can be inherited and withdrawn on interrupt; 'still running' corrections\n\nRemote tool calls can take over a standing request on resume, withdraw it on interrupt, and report hosts as still running or restarted\n\n**Unclear.** The finding does not say what a standing request is or what a user sees when one is withdrawn.\n\n**What**\n\nA remote tool call is an action Claude runs on another machine, a host. This handling changes in several ways:\n\n- On resume, a call can take over an existing standing request instead of starting a new one, and withdraws it if the call is cancelled.\n\n- A result that arrives late can now be corrected to 'still_running', with a quiet period after a stop.\n\n- A host whose epoch has changed is marked 'host_restarted', recorded as 'source: inferred' because it is deduced, not reported.\n\n- Hosts are only asked about outcomes if Claude Code has a connection to them.\n\nThis area involves the `tengu_remote_tool_targets` gate, a server-controlled switch.\n\n**Why**\n\nInterrupting a resumed remote call can withdraw the work it took over, and a restarted or still-busy host is reported as such."}