{"version":"2.1.290","anchor":"pending-tool-use-tracking-added-to-session-historyresume-lo","canonical_anchor":"pending-tool-use-tracking-added-to-session-historyresume-lo","heading":"Better tracking of unanswered tool calls when rebuilding a session","tier":"internal","area":"Resume","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/pending-tool-use-tracking-added-to-session-historyresume-lo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Better tracking of unanswered tool calls when rebuilding a session\n\nWhen a session is rebuilt from its history, Claude Code now checks which tool calls never got a result\n\n**Unclear.** It is not clear what Claude Code does with the list of unanswered tool calls once it has it.\n\n**What**\n\nA tool call is a request from Claude to run one of its tools, such as reading a file or running a command, and each one normally gets a result back. When Claude Code rebuilds a session from its saved message history, it now goes through the messages and collects the identifiers of every tool call and every tool result. A tool call counts as handled when it has a matching result or has already been marked as handled. This pass also filters the list of connected MCP servers (outside programs that offer Claude extra tools).\n\n**Why**\n\nThis could change how resumed or remote sessions deal with tool calls that were left without an answer, for example when a session stopped partway through a step.\n\n- Area: Resume\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}