{"version":"2.1.259","anchor":"remote-tool-calls-now-survive-session-restarts-with-explicit","canonical_anchor":"remote-tool-calls-now-survive-session-restarts-with-explicit","heading":"Remote tool calls now survive session restarts with explicit status messaging","tier":"notice","area":"Remote Tools","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/remote-tool-calls-now-survive-session-restarts-with-explicit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### Remote tool calls now survive session restarts with explicit status messaging\n\nTool calls sent to remote hosts are tracked so a session restart can adopt them and explain whether the command actually ran.\n\nA new tracking class records tool calls dispatched to remote hosts in `in_flight_served_calls`. On restart, it tries to adopt these in-flight calls and generates detailed status messages depending on whether the command definitely ran, was still pending approval, or its fate is unknown, including messaging that the session restarted while a command was under way.\n\n- Area: Remote Tools\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}