docs(rfd): Session Rewind#1214
Open
htahaozlu wants to merge 1 commit into
Open
Conversation
Author
|
@cla-bot check |
Author
|
@cla-bot check |
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.
This RFD proposes adding
session/rewindandsession/edit_promptmethods to ACP, enabling user-facing conversation rewind and message editing — features universally present in coding-agent UIs (Claude Desktop, Cursor, Windsurf, Gemini CLI checkpointing) but currently lacking a portable protocol surface.Builds on
unstable_message_id(already inCargo.toml'sunstableset).Complementary to, and distinct from,
session/fork: fork is non-destructive context copying for side queries; rewind mutates the session timeline in place.Consolidates two previously scattered discussions:
session/undoandsession/redorequestsFilesystem rollback is explicitly out of scope (see Status quo and FAQ in the RFD body) — left to existing
fs/*methods,session/fork, IDE-native snapshots, or the user's SCM.Concrete user-facing bugs in Zed that motivate a portable protocol surface:
/clearis lost on Zed restartStatus: Draft proposal, open for champion from the core team. Happy to iterate on the design — open to splitting into separate RFDs (rewind vs edit-prompt), merging with related work, or scoping down to a single primitive if preferred.
CLA: will sign at https://zed.dev/cla before any implementation PR. Posting this RFD PR per the RFD process so the design discussion can happen against concrete text.