session/resume idempotency #1824
LucaDiba
started this conversation in
Protocol Suggestions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Claude and Codex allow calling
session/loadmultiple times on the same session. GitHub Copilot errors withSession {} is already loaded.Streamable HTTP & WebSocket Transport mentions that "A session persists on the server independently of any one connection, so after a dropped connection a client can reconnect and resume it via session/load."
But I couldn't find any reference to this in the docs outside of this sentence in the RFD.
Should we add something like "session/resume MUST be idempotent" in the v2 (and v1? even though this is not the case today) Session Setup page?
All reactions