RFD: session/list API for session discovery and management #211
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
Proposes a new session/list endpoint to enable: - Discovery of existing sessions - Session history browsing - Multi-session management - Better UX for resuming conversations The endpoint supports: - Filtering by creation date, access date, and working directory - Pagination with limit/offset - Sorting by various criteria - Optional capability for agents with session persistence Includes detailed JSON-RPC request/response examples and addresses common questions about alternatives, interaction with session/load, and pagination strategies.
yordis
reviewed
Oct 29, 2025
yordis
reviewed
Oct 29, 2025
Replace metadata with _meta in docs/rfds/sessions-list-api.mdx Update JSON response example and response field list Keep prose references to “metadata” unchanged
benbrandt
reviewed
Oct 30, 2025
Major changes to sessions-list-api.mdx: - Switch from offset-based to cursor-based pagination using continuation tokens - Rename `lastAccessedAt` to `updatedAt` for consistency across the API - Remove `preview` field from SessionInfo (out of scope for this RFD) - Remove session orphaning from problem statement - Replace `sortBy`/`sortOrder` parameters with `search` parameter - Remove `total` count from response (incompatible with cursor pagination) - Update all request/response examples to reflect new pagination model - Clarify response includes `hasMore` and `nextContinuationToken` instead of `total`
benbrandt
reviewed
Oct 31, 2025
Comment on lines
+141
to
+142
| - `hasMore` (boolean) - Whether more results are available after this page | ||
| - `nextContinuationToken` (string, optional) - Pass this token in the next request's `continuationToken` to fetch the next page |
There was a problem hiding this comment.
What do you think of following MCP's pattern here?: https://modelcontextprotocol.io/specification/2025-06-18/server/utilities/pagination
They call it nextCursor and you use the presence of it for the same meaning as your hasMore boolean, which I think makes sense
|
I think this is already well on it's way to "Preview" stage. In the spirit of the process, I am going to go ahead and merge this as-is as a "draft" and we can keep iterating on it for getting it ready for "Preview" and then we can "Accept" and start working on it. Thanks so much for the work here! |
|
Draft published here: https://agentclientprotocol.com/rfds/session-list |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Proposes a new session/list endpoint to enable:
The endpoint supports:
Includes detailed JSON-RPC request/response examples and addresses common questions about alternatives, interaction with session/load, and pagination strategies.