What
Every background task reported through stream-JSON and SDK output now describes itself more fully: what kind of task it is, which agent owns it, what shell a local bash task runs under, and whether it is an ambient housekeeping task rather than something the user started. Ambient tasks can be kept out of the transcript while still showing up in task lists, and a change to that flag now counts as a change in its own right, so listings refresh when it flips rather than only when tasks join or leave the set.
Details
- The report gained the fields
task_type,owner_agent_id,shell_kind,ambientandobserver_owned. owner_agent_ididentifies the owning agent for bash, MCP and websocket monitor tasks.- The SDK schema gained an optional boolean
ambienton the task started, task updated and task list frames. - Because
ambientis optional, tasks that do not set it behave exactly as before. - Consumers that rebuild their whole task set from each payload will now see emissions where nothing was added or removed, only an existing task's
ambientflag changed.
Evidence
or an entry's \ambient\ flag flips, owner_agent_id
Strings lifted out of the shipped bundle, so the claim above can be checked against them.