Conversation
…gg#9897) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…ingdotgg#8464) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Julius Marminge <julius0216@outlook.com>
…gg#9907) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Julius Marminge <julius0216@outlook.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Julius Marminge <julius0216@outlook.com>
…otgg#9905) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…gg#9928) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…dotgg#9920) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…ngdotgg#10051) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Julius Marminge <julius0216@outlook.com>
…dotgg#12966) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…tgg#12967) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Background-task notifications and delegated completions queued behind a held queue are hidden from the queue UI, so the Resume queue control never appeared, yet thread.settle counted them as active work. Settle now cancels those automatic runs in the same transaction; user-queued messages still block it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Keep main's recycled mobile list and per-row clock scoping alongside V2 runtime ownership, subagent filtering, and unread completion labels. Preserve provider compatibility diagnostics and shared PR badge controls while retaining V2 authentication actions and linked-PR tooltips. Port main's PR batching and settlement quota improvements into the V2 services.
mwolson
added this pull request to stack #36
September 27, 2026 21:48
mwolson
force-pushed
the
contrib/ctm/delegated-sibling-delivery
branch
from
September 30, 2026 20:01
deb452e to
e925b7f
Compare
mwolson
force-pushed
the
contrib/ctm/exhausted-start-settlement
branch
2 times, most recently
from
October 1, 2026 12:38
af0d444 to
5fe2c77
Compare
mwolson
removed this pull request from stack #36
October 1, 2026 12:39
Owner
Author
|
Absorbed upstream by pingdotgg#13938 delegated-completion-no-cap; the cancellation guard from this layer now lives in #23 cancelled-delivery-recovery. Closing; the branch is kept. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
14 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Changed
A parent agent that delegates several tasks is now woken for every sibling result, however many finish after its earlier wakes. Results that arrive while a wake is in flight are batched into the next one. Archived or deleted parents, cancelled deliveries and real queued user messages are left alone.
Why
Each group of sibling tasks allowed only an initial delivery and one follow-up. Any sibling that finished after that stayed pending and was visible only through
task_status, so parents that ended their turn as instructed never learned the rest of their results.Checklist