{"version":"2.1.268","anchor":"task-status-tool-result-now-conditionally-omits-output-file","canonical_anchor":"task-status-tool-result-now-conditionally-omits-output-file","heading":"Task-status tool result now conditionally omits output file path based on available tools","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/task-status-tool-result-now-conditionally-omits-output-file","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Task-status tool result now conditionally omits output file path based on available tools\n\nBackground task status can now omit the output file path depending on which tools are available\n\n**What**\n\nWhen reporting the status of a background task, Claude Code now checks which tools are available to it. If that check fails, the report omits the output file path, forcing the task to report back only via `SendMessage` rather than pointing to a saved output file. This is in addition to an existing check based on `webFetchSavedFiles`.\n\n**Why**\n\nThis prevents background tasks from referencing an output file path in cases where the tools needed to make use of it aren't actually available.\n\n- Area: Elsewhere\n- Names: `SendMessage`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}