{"version":"2.1.281","anchor":"subagent-handback-takes-outputfile-from-the-task-record","canonical_anchor":"subagent-handback-takes-outputfile-from-the-task-record","heading":"Agent task output file now comes from the task record and may be absent","tier":"internal","area":"Agents","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/subagent-handback-takes-outputfile-from-the-task-record","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Agent task output file now comes from the task record and may be absent\n\nSubagent tasks now take their output file path from the task record, and output polling skips tasks that have no output file\n\n**Unclear.** The finding does not say whether the two ways of getting the file location ever gave different answers.\n\n**What**\n\nA subagent is a helper agent Claude starts to work on part of a task. Each one has a task record, and until now its output file path was always worked out from the agent's id.\n\n- When a subagent launch is awaited, the result's `outputFile` now comes from the task record (`W.outputFile`) instead of being computed from the agent id. Another task-spawn return does the same.\n\n- The code that follows a running background agent's output now also requires `outputFile !== void 0`, so tasks without an output file are skipped instead of being read.\n\n**Why**\n\nIn practice some agent tasks may now have no output file, or one outside the usual per-id location, and Claude Code no longer assumes every running task has one.\n\n- Area: Agents\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}