Delegation owner-death loses finished child work/transcripts
Cluster 116000. Data as of
Nothing open on GitHub. Fix merged in #117654 on 21 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #117654. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #117654. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a bug where killing or orphaning a delegation owner causes completed subagent work and terminal transcripts to be lost, reporting 'outcome unknown' for tasks that already finished. The changes aim to preserve finished child results and include transcript paths and git state in recovery notices.
Open issues0
Open PRs0
Fixes on record
-
#116707 fix(delegation): finished subagent work survives owner death and recovery notices carry transcript paths (#116000, salvage #116034 #116058)
files:
tests/tools/test_async_delegation.py,tests/tools/test_delegation_recovery_diagnostics.py,tools/async_delegation.py,tools/delegate_tool_dispatch.py,tools/process_registry_notifications.py -
#117654 feat(delegation): owner-death recovery event includes transcript tails and git state so the parent can continue without forensics (#116000)
files:
tests/tools/test_delegation_recovery_diagnostics.py,tools/async_delegation.py,tools/async_delegation_recovery_hints.py,tools/process_registry_notifications.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#116034 fix(delegation): a one-child detached unit keeps its finished child on owner death · merged via another change →
b851bd1,#116707
Closed issues · 1
- Closed#116000[Bug]: delegation owner death (OOM-kill / orphaning) loses children's terminal records and completed work — 'outcome unknown' delivered for tasks that finished
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the Lab