RelatedRequestId routing for MCP streams#26562
Conversation
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
f27587e to
9740b08
Compare
|
Preview URL: https://9740b082.preview.developers.cloudflare.com Files with changes (up to 15) |
irvinebroque
left a comment
There was a problem hiding this comment.
Generating docs like this from PRs seems to be working really well — this all reads really well
Add documentation explaining how the Agents SDK routes server-to-client requests through the correct HTTP stream using the relatedRequestId parameter. This is particularly important for elicitation requests that need to flow through the same bidirectional stream as the tool call that triggered them. Includes: - Explanation of the routing behavior and priority - Code example showing how to use relatedRequestId with elicitInput - Technical details about stream mapping 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
9740b08 to
57bf652
Compare
|
Updated documentation to reflect the latest changes from cloudflare/agents#654 The documentation now includes:
This ensures developers understand how to properly route server-to-client requests through the correct HTTP stream when using elicitation or other bidirectional communication patterns. |
|
blocking this. I want to move the elicitations example out into its own page. This pr can be a couple of lines explaining the different streams and how request ids work |
|
Hey there, we've marked this pull request as stale because there's no recent activity on it. This label is helps us identify PRs that might need updates (or to be closed out by our team if no longer relevant). |
|
Hey there, we've closed out this pull request because it's been stale for a while and there's been no additional action on it. If these changes are still relevant, open a new pull request (or flag to us in a GitHub issue). |
Syncs documentation changes from cloudflare/agents#654
Changes
This PR documents the relatedRequestId routing feature for bidirectional MCP streams in the Streamable HTTP transport.
Added to transport.mdx:
This feature enables proper server-to-client request routing, ensuring that server-initiated requests (like elicitation) are delivered through the correct bidirectional stream while maintaining proper request-response pairing.
Related PR: cloudflare/agents#654