Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.281 ·

Background shell and workflow tasks record their output file while running

Local bash and local workflow tasks, including paused workflows, now store an outputFile path in their task state

Group of 2 Under the hood Internal Changes
JSON All of v2.1.281
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.281,
Internal ChangesSection of the release

What

Claude 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:

  • All three kinds of local_bash task store outputFile: background tasks, foreground tasks and adopted tasks.
  • local_workflow tasks store outputFile when they are created.
  • Paused local_workflow tasks also include outputFile.

Before, the output file appeared only as terminal.output_file once a task had finished.

Why

In practice, the location of a task's output is known while the task is still running or paused, not only after it ends.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say whether the stored path is shown to you or used anywhere else.

See this entry in the whole of v2.1.281 →

Feedback