Under the hood
Useful1 Signal2
Queued task notifications now record whether they were delivered or dropped because the agent stopped.
What's wrong with this entry?
Anonymous. No account, no email.
What
Both the interactive and the headless routers that deliver task notifications now attach a reason when clearing queued events: delivered_to_agent once delivery is committed, and agent_stopped when the target agent has stopped and the events are discarded. Previously the calls passed only the list.
Evidence
delivered_to_agent
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