{"version":"2.1.248","anchor":"backgrounded-shell-commands-may-return-a-structured-task-ack","canonical_anchor":"backgrounded-shell-commands-may-return-a-structured-task-ack","heading":"Backgrounded shell commands may return a structured task acknowledgement","tier":"soon","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/backgrounded-shell-commands-may-return-a-structured-task-ack","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Backgrounded shell commands may return a structured task acknowledgement\n\nBackgrounded shell commands may return a structured task record instead of raw output.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- Affects the PowerShell tool and the parallel bash path.\n- 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\"`.\n- Wording varies by session: in a single-shot print session the message says the command is stopped when the turn ends.\n- The guard is a single-argument predicate; one candidate definition in this build is a stub that returns false.\n\n**Evidence**\n\n`tengu_bash_task_ack`\n\n- Area: Background Tasks\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}