{"version":"2.1.285","anchor":"remote-tool-restart-adoption-routing-reworked","canonical_anchor":"remote-tool-restart-adoption-routing-reworked","heading":"Tool calls picked up after a remote restart now carry their original host","tier":"internal","area":"Remote Tools","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/remote-tool-restart-adoption-routing-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Tool calls picked up after a remote restart now carry their original host\n\nAfter a restart, Claude Code fills in the remote host for adopted tool calls that lack one, under certain conditions\n\n**Unclear.** The conditions under which the host is filled in are not stated.\n\n**What**\n\nClaude Code can run tool calls on remote hosts and, after a restart, take over (adopt) calls that were still under way. It now looks up the adopted state first and, under certain conditions, adds the adopted host to the tool call when the call does not name one. It still refuses a call that would otherwise run on this machine. Before, it did its routing check first and never filled in the host.\n\n**Why**\n\nIt changes where tool calls are sent after a remote restart.\n\n- Area: Remote Tools\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}