Repository navigation
docs(rfd): drop JSON-RPC batches from the HTTP/WebSocket transport - #2729
Merged
Merged
Conversation
v2 removed JSON-RPC batching, so the transport no longer answers arrays with 501 or plans batch support. A JSON array gets a single -32600 error response with id null (400 Bad Request over HTTP), matching the core transport rule. Co-Authored-By: Claude <noreply@anthropic.com>
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.
v2 removed JSON-RPC batching (#2625), but the Streamable HTTP/WebSocket transport RFD still says batch requests return
501and may be added later.This aligns the RFD with the core rule:
400 Bad Requestwith a single JSON-RPC error response (-32600,id: null), and none of its entries are processed.-32600response.The TypeScript and Rust SDKs are being updated to match in their schema 1.14 sync.