[FEATURE] Per-prompt rewind/undo in Desktop App

Resolved 💬 6 comments Opened Apr 5, 2026 by xoxoname Closed Jun 16, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

When working on multi-step coding tasks, I often need to undo changes from a
specific prompt while keeping changes from other prompts intact. In the Desktop
App, there's no way to do this — /rewind returns "Unknown skill" and
Esc+Esc does nothing.

My typical workflow: I ask Claude to make 5-6 changes across a session.
Change #3 broke something, but changes #4-6 are fine. I need to revert only
#3, but the Desktop App gives me no way to go back to a specific point.
I end up manually reading git diffs and hand-reverting lines, which is slow
and defeats the purpose of using an AI editor.

The CLI version supports /rewind — but I use the Desktop App as my primary
interface, and this core functionality is missing from it.

Proposed Solution

Add a rewind/checkpoint UI to the Desktop App conversation view:

  1. Each user prompt in the conversation acts as a checkpoint
  2. Hovering over a message reveals a "Revert to here" button
  3. Clicking it shows a diff preview of what will be rolled back
  4. User can select/deselect individual files before confirming
  5. After reverting, the conversation history remains visible

(greyed out) so context isn't lost

This matches the behavior already available in the CLI via /rewind,
adapted for a graphical interface.

Alternative Solutions

  • Using git diff and manually reverting specific hunks — works but tedious
  • Asking Claude to "undo your last change" — unreliable, wastes context,

and Claude sometimes makes additional unintended modifications

  • Switching to the CLI version just for /rewind — disrupts workflow
  • Using competing tools (Cursor, Windsurf) that have this built in

Priority

Critical - Blocking my work

Feature Category

File operations

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗