{"version":"2.1.281","anchor":"adopting-served-remote-tool-calls-after-a-restart-is-compile","canonical_anchor":"adopting-served-remote-tool-calls-after-a-restart-is-compile","heading":"Adopting served remote-tool calls after a restart is compiled off","tier":"soon","area":"Remote Tools","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/adopting-served-remote-tool-calls-after-a-restart-is-compile","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Adopting served remote-tool calls after a restart is compiled off\n\nA new path for presenting adopted host tools after a restart was added, but a built-in switch keeps it empty\n\n**What**\n\nThis build adds `presentAdoptedHostTools` and a new `provisional_host_tools` field on the `tengu_remote_tool_restart_adoption` event. Both handle tool calls that were still running when a worker restarted in headless print mode.\n\nWhether those calls are adopted depends on an internal switch, and in this build that switch always returns false. The list of calls to adopt is therefore always empty, and the new presentation path receives nothing. The same switch empties the restore list when a session is resumed.\n\n**Why**\n\nIn this build, after a restart, in-flight calls are not picked back up through this path.\n\n- Area: Remote Tools\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}