Cancelling while a background agent is resuming now stops it instead of reporting a read failure.
What's wrong with this entry?
Resuming a background agent reads its transcript; that read now receives the abort signal, re-checks it immediately afterwards, and raises the cancellation error. Previously an in-flight resume would run to completion and then be reported as a transcript read failure.
- Abort errors are rethrown before the existing read-failure telemetry and transient-error classification, so cancellations no longer show up as failures.
subagent_resume_setup_read_failed
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.232
Background dialog gains a Completed section and lets you stop finished agents
Both mention background agent
-
v2.1.232
Task list keeps your place, and Enter opens a running agent
Both mention background agent
-
v2.1.234
Background agent failures are labelled with a clearable reason
Both mention background agent