RelatedRequestId routing for MCP streams #26562
Open
Conversation
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
threepointone
requested review from
a team,
elithrar,
irvinebroque,
rita3ko and
thomasgauvin
as code owners
github-actions
bot
added
size/s
product:agents
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
threepointone
force-pushed
the
sync-docs-pr-654
branch
from
f27587e to
9740b08
Compare
Contributor
|
Preview URL: https://9740b082.preview.developers.cloudflare.com Files with changes (up to 15) |
irvinebroque
approved these changes
Nov 17, 2025
Contributor
irvinebroque
left a comment
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 <[email protected]>
threepointone
force-pushed
the
sync-docs-pr-654
branch
from
9740b08 to
57bf652
Compare
Contributor
Author
|
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. |
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.
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