Repository navigation
docs(coding-agent): document subagent escalation behavior - #122
Merged
Issacboy123 merged 1 commit intoAug 28, 2026
Merged
Issacboy123 merged 1 commit into
Issacboy123 merged 1 commit into
Conversation
Pepps233
force-pushed
the
docs/document-subagent-escalations
branch
from
August 25, 2026 14:36
088299f to
f22697b
Compare
Pepps233
self-requested a review
August 25, 2026 18:35
Pepps233
approved these changes
Aug 25, 2026
Issacboy123
force-pushed
the
docs/document-subagent-escalations
branch
from
August 27, 2026 10:54
187dd69 to
1d4b235
Compare
Issacboy123
force-pushed
the
docs/document-subagent-escalations
branch
from
August 27, 2026 23:11
1d4b235 to
35a70ac
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.
Summary
This PR explains how child-to-parent escalation reports work and when children should use them. It covers report limits, delivery while the parent is active or idle, behavior while the parent waits for children, and availability after a saved child is woken. It also clarifies that reports are hidden but still untrusted session data and records the feature in the coding-agent changelog.
This PR is stacked on
fix/complete-subagent-coordination, which completes escalation-aware coordinated waiting.Reasoning
The usage guide is the natural home for operational behavior, while the sessions and SDK guides clarify persistence and construction boundaries where users already encounter subagents. Describing acknowledgement, hidden delivery, and storage separately avoids implying model consumption, crash durability, secrecy, or redaction beyond the implemented guarantees.
Changes
escalate_to_parentin the SDK documentation and added an Unreleased coding-agent changelog entry.Testing
node ../../node_modules/vitest/dist/cli.js --run test/suite/subagent-parent-messaging.test.ts test/suite/subagent-services.test.ts test/suite/subagent-registration.test.ts test/suite/subagent-actions.test.ts test/suite/subagent-coordination.test.ts test/suite/subagent-persistence.test.ts test/suite/agent-session-queue.test.ts test/subagent-controller.test.tsnpm.cmd run checkgit diff --check