Backgrounded shell commands may return a structured task record instead of raw output.
Both the record and its telemetry sit behind one unresolvable check.
What's wrong with this entry?
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.
- Affects the PowerShell tool and the parallel bash path.
- New telemetry event
tengu_bash_task_ackrecords the trigger (user,turn_abort,timeoutorexplicit), whether the task ends with the final response, andshell: "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.
tengu_bash_task_ack
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Background task notifications arrive inside a system-reminder
Both mention background task
-
v2.1.235
Several finished background tasks now report as one line
Both mention background task
-
v2.1.236
Background-task notices no longer look like user approval
Both mention background task