Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.248 ·

Backgrounded shell commands may return a structured task acknowledgement

Backgrounded shell commands may return a structured task record instead of raw output.

Nothing to try yet In Development
JSON All of v2.1.248
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Background TasksArea: what it touches
In DevelopmentKind: in v2.1.248,
In DevelopmentSection of the release

Both the record and its telemetry sit behind one unresolvable check.

What

When a shell command is sent to the background, the tool result can now be a structured task record with a status of working, a task id and a status message, instead of the joined stdout and stderr text used before. Both this and its telemetry sit behind one unresolved check, so whether it is active on this build is not decided by anything nameable in the source.

Details
  • Affects the PowerShell tool and the parallel bash path.
  • New telemetry event tengu_bash_task_ack records the trigger (user, turn_abort, timeout or explicit), whether the task ends with the final response, and shell: "powershell".
  • Wording varies by session: in a single-shot print session the message says the command is stopped when the turn ends.
  • The guard is a single-argument predicate; one candidate definition in this build is a stub that returns false.
Evidence

tengu_bash_task_ack

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.248 →

Feedback