[Agents] DO NOT MERGE: Document sub-agent workflows#30491
Draft
threepointone wants to merge 1 commit into
Draft
Conversation
Clarify how workflows started from sub-agent facets are tracked, controlled, and routed through AgentWorkflow. Made-with: Cursor
github-actions
Bot
added
product:agents
github-actions
Bot
assigned
elithrar,
irvinebroque,
rita3ko,
thomasgauvin and
whoiskatrin
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
Contributor
Contributor
|
Hey there, we've marked this pull request as stale because there's no recent activity on it. This label helps us identify PRs that might need updates (or to be closed out by our team if no longer relevant). |
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
6 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.
Summary
Updates Agents documentation for the SDK changes in cloudflare/agents#1430. The docs now explain how workflows started from sub-agent facets are tracked, how
AgentWorkflow.agentroutes back to the originating facet, whyagentBindingrefers to the root Agent binding for sub-agent callers, and how parents should use child-defined wrapper methods for workflow controls becauseSubAgentStub<T>does not expose inheritedAgentmethods.Documentation checklist
Made with Cursor