Repository navigation
Assumption of Sampling and session might be wrong? #119
Description
Hi all,
@tzolov points here the following:
Key point: according to the spec, you can only use listRoots or createMessages within an existing client session. This means these client features are only accessible from within tool/prompt/resource handlers using the new exchange argument.
I have read and re-read the spec but I'm unable to find any mention to that at all.
Even the diagram doesn't seem to sustain that hypothesis:
sequenceDiagram
participant Server
participant Client
participant User
participant LLM
Note over Server,Client: Server initiates sampling
Server->>Client: sampling/createMessage
Note over Client,User: Human-in-the-loop review
Client->>User: Present request for approval
User-->>Client: Review and approve/modify
Note over Client,LLM: Model interaction
Client->>LLM: Forward approved request
LLM-->>Client: Return generation
Note over Client,User: Response review
Client->>User: Present response for approval
User-->>Client: Review and approve/modify
Note over Server,Client: Complete request
Client-->>Server: Return approved response
Would it be possible to discuss the exact point of the spec that refers to this? I'm unable to find it.
Activity
chemicL commentedon Feb 17, 2026
I think at the time this was discussed there was a lot of ambiguity on this subject. The recent modelcontextprotocol/modelcontextprotocol#2260 proposal should make things more explicit in order to prepare for a stateless-by-default transport implementation.
Can we take a step back and understand whether there is a particular interaction flow that you are interested in that can not be achieved with the current SDK design?
Kehrlann commentedon Jun 25, 2026
As @chemicL mentioned, this has been addressed in SEP-2260, closing.