{"version":"2.1.281","anchor":"resume-passes-host-answerable-tool-use-ids","canonical_anchor":"resume-passes-host-answerable-tool-use-ids","heading":"Resume passes host-answerable tool-use IDs","tier":"internal","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/resume-passes-host-answerable-tool-use-ids","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Resume passes host-answerable tool-use IDs\n\nResuming in print mode now works out which tool calls the host can answer and passes them to session loading\n\n**Unclear.** The finding does not say what makes a tool call host-answerable or how the resumed session treats those calls differently.\n\n**What**\n\nWhen you use `--continue` or `--resume` in print mode (the one-shot, non-interactive mode), Claude Code now builds a list of `hostAnswerableToolUseIds` from the restored worker state and the list of tools. It passes that list to session loading. A tool use is a single request from Claude to run a tool.\n\nLoading a remote session now uses `deserializeRemoteSessionLog`. Plan-mode and restore handling were merged into one shared step.\n\n**Why**\n\nOn resume, Claude Code now knows which pending tool calls the host can still answer.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}