What
A subagent is a helper Claude starts for a separate task, and a background subagent keeps running while you work. Waking and resuming these agents changed.
- Idle background agents are now woken by more kinds of queued items, not only task notifications. The timer that checks the queue again reacts to the same wider set.
- A wake with no notification prompts is marked
resultsOnly, and resume accepts aresultsOnlysetting. - Failed results-only wakes are counted, and an agent whose resume keeps failing is dropped.
- Waking agents no longer requires the main-loop context to be present first.
- Resumed agents, and agents started from the main conversation, are tagged
spawnedByMainThread. - Separately, copying git branches into a builder now fails with a message saying HEAD changed while the branches were being read, if HEAD moved during the read.
Why
In practice, results from background agents should arrive more reliably, and an agent that cannot be resumed is dropped instead of being retried without end. This may also change when idle background agents wake up.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Part of the new wake-up path may not run yet, and it is not clear what decides the extra cases that trigger a check.