{"version":"2.1.281","anchor":"background-bash-tasks-record-outputfile","canonical_anchor":"background-bash-tasks-record-outputfile","heading":"Background shell and workflow tasks record their output file while running","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/background-bash-tasks-record-outputfile","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Background shell and workflow tasks record their output file while running\n\nLocal bash and local workflow tasks, including paused workflows, now store an outputFile path in their task state\n\n**Unclear.** The finding does not say whether the stored path is shown to you or used anywhere else.\n\n**What**\n\nClaude Code can run shell commands and workflows as tasks in the background. Their task state now includes an `outputFile` path, the file their output is written to:\n\n- All three kinds of `local_bash` task store `outputFile`: background tasks, foreground tasks and adopted tasks.\n\n- `local_workflow` tasks store `outputFile` when they are created.\n\n- Paused `local_workflow` tasks also include `outputFile`.\n\nBefore, the output file appeared only as `terminal.output_file` once a task had finished.\n\n**Why**\n\nIn practice, the location of a task's output is known while the task is still running or paused, not only after it ends.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}