fix: WorkerTransport doesn't persist clientCapabilities, breaking elicitation in serverless #27667
+17
−3
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
agents-git-bot
bot
requested review from
a team,
elithrar,
irvinebroque,
rita3ko,
thomasgauvin,
threepointone and
whoiskatrin
as code owners
github-actions
bot
added
product:agents
github-actions
bot
assigned
elithrar,
irvinebroque,
rita3ko,
thomasgauvin,
threepointone and
whoiskatrin
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
Contributor
|
Preview URL: https://ff4bf506.preview.developers.cloudflare.com Files with changes (up to 15) |
Update documentation to reflect PR cloudflare/agents#783 changes: - Updated TransportState interface to include initializeParams field - Added documentation explaining that client capabilities, client info, and protocol version are now persisted and restored across serverless restarts - Emphasized importance of capability persistence for elicitation and sampling features - Added detailed field descriptions for TransportState interface This enables MCP servers to properly support advanced client features like elicitation after serverless cold starts. Related: cloudflare/agents#783 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
agents-git-bot
bot
force-pushed
the
sync-docs-pr-783
branch
from
7704885 to
e6a5a43
Compare
Updates documentation to reflect that WorkerTransport now persists client capabilities across serverless restarts. This fixes an issue where elicitation and other capability-dependent features would fail after hibernation or cold starts. Changes: - Add initializeParams to TransportState interface documentation - Document that client capabilities are persisted and restored - Clarify the behavior of state restoration Related to cloudflare/agents#783 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
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
Document the new client capabilities persistence feature in
WorkerTransportfrom cloudflare/agents PR #783.Changes
Updated
/agents/model-context-protocol/mcp-handler-api/documentation to reflect:initializeParamsfield inTransportStateinterface that stores client capabilities, clientInfo, and protocolVersioninitializeParamsfieldContext
The original PR (cloudflare/agents#783) fixed a critical bug where client capabilities were not persisted in serverless environments. This caused features like elicitation to fail after Durable Object/Agent hibernation.
The fix ensures that when using
WorkerTransportwith persistent storage, client capabilities are:This documentation update makes developers aware of this behavior and the new fields in
TransportState.Related PR