{"version":"2.1.273","anchor":"session-resume-findunresolvedtooluse-now-used-directly-inst","canonical_anchor":"session-resume-findunresolvedtooluse-now-used-directly-inst","heading":"Session-resume: findUnresolvedToolUse now used directly instead of storageV5 field","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/session-resume-findunresolvedtooluse-now-used-directly-inst","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Session-resume: findUnresolvedToolUse now used directly instead of storageV5 field\n\nSession resume in print mode now finds unresolved tool calls directly instead of via a stored storageV5 field\n\n**What**\n\nWhen resuming a session in print mode, Claude Code now looks up any unresolved tool call (a tool invocation that never got a result recorded) by calling a dedicated `findUnresolvedToolUse` lookup directly, instead of reading it from a `storageV5` field that was passed through.\n\n**Why**\n\nThis is an internal implementation change to how session resume locates unfinished tool calls; it should not change what you experience when resuming a session.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}