{"version":"2.1.259","anchor":"mcp-session-resume-can-adopt-served-tool-calls-left-in-fligh","canonical_anchor":"mcp-session-resume-can-adopt-served-tool-calls-left-in-fligh","heading":"MCP session resume can adopt served tool calls left in-flight by a prior worker","tier":"notice","area":"Remote Tools","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/mcp-session-resume-can-adopt-served-tool-calls-left-in-fligh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### MCP session resume can adopt served tool calls left in-flight by a prior worker\n\nResuming an MCP session can adopt tool calls a previous worker left in flight instead of re-issuing the interrupted turn.\n\nWhen an MCP session resumes, tool calls that a previous worker process had already dispatched but not yet resolved (\"served calls\") can now be adopted directly by the new process instead of re-issuing the interrupted turn. The model is told which calls' results were lost via an \"orphaned-permission\" meta-message, and adoption is logged as `tengu_remote_tool_restart_adoption`.\n\n- Area: Remote Tools\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5"}