Repository navigation
fix(server): let coordinators settle agents after follow-ups - #47
Merged
Merged
Conversation
github-actions
Bot
added
vouch:trusted
nickrroberts
force-pushed
the
feat/coordinator-owned-settling
branch
from
September 29, 2026 21:59
98a7435 to
8cf00a3
Compare
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
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.
Project agents currently settle as soon as their result is delivered, including continuation reports. This can hide agents that still have follow-up work.
Remove the post-push settlement dispatch and its unused receipt helper and query fields. Delivery receipts and deduplication stay intact. Coordinator prompts, agent tool descriptions and user docs now keep agents available for follow-ups and direct the coordinator to use cp_agent_settle once work is complete and no follow-ups remain. The global merge-based settlement policy and setting are unchanged.
Validation after a conflict-free rebase onto main, after release 0.0.57 was published:
Model: GPT-6. Harness: Codex.