{"version":"2.1.287","anchor":"stream-json-tool-use-result-documents-detachedtoolcall","canonical_anchor":"stream-json-tool-use-result-documents-detachedtoolcall","heading":"Web fetches and searches can now report that they stepped aside for your message","tier":"notice","area":"SDK","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/stream-json-tool-use-result-documents-detachedtoolcall","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Web fetches and searches can now report that they stepped aside for your message\n\nIn stream-json output, a WebFetch or WebSearch result can now carry detachedToolCall: true, meaning it is still running\n\n**Unclear.** Exactly what makes a web call step aside is not spelled out beyond its happening for a user message.\n\n**What**\n\nWhen Claude Code writes its output as stream-json (a stream of structured messages that programs built on Claude Code read), each tool result is described in a fixed format. That description now covers one more case: a `WebFetch` or `WebSearch` call that stepped aside for a message from the user carries `{ detachedToolCall: true }`.\n\nThis means the call is still running. Its real result reaches the model in a later turn.\n\n**Why**\n\nIf you build on Claude Code's SDK or read its stream-json output, a result with `detachedToolCall: true` is not the final answer, so your code should not treat it as an empty or failed fetch and should expect the real result later.\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}