Repository navigation
RFD: Read session text without activating the session - #2753
Draft
slapoguzov wants to merge 1 commit into
Draft
slapoguzov wants to merge 1 commit into
slapoguzov wants to merge 1 commit into
Conversation
Preview approval requiredThis pull request comes from a fork, so Mintlify won't build a preview until someone with write access approves commit |
This branch has not been deployed
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.
Clients can discover sessions through
session/list, but reading their history through resume also activates the session. This RFD proposes optionalsession/read_textin v1 and v2: a paginated projection of retained user, Agent and displayable compaction-summary text for a known session, without lifecycle or connection changes.The proposal defines byte bounds, snapshot cursors, retention and access checks. Clients keep their own matching semantics; server-side search and full transcript replay are discussed as alternatives. This is a contract proposal only, with no schema or runtime implementation.
Validation: independent contract and privacy review; pinned Prettier and typos checks; JSON examples and navigation parsing; scoped diff checks. Five future implementation acceptance cases are included in the RFD. Runtime acceptance is not claimed.