[Bug] /rewind default option unsafe: rolls back code without confirmation or clear warning

Resolved 💬 4 comments Opened Apr 19, 2026 by Rob-Morris Closed May 26, 2026

Bug Description
/rewind has a big UX footgun. The default option, "code and conversation", is an unsafe destructive operation that rolls back context AND code touched (directly by Claude tools) during the session.

  1. This is not at all clear. "code and conversation" (and "code") are not presented as a dangerous options that might result in loss of work
  2. "Code and conversation" is bad as the default: accidentally triggering this command and hitting enter = loss of data
  3. Rollbacks are inconsistent: only what claude touched with internal tools
  4. There's no confirmation before proceeding with the dangerous op, no listing of what will be rolled back, hard to assess blast radius.
  5. /rewind has dual use, as recovery tool but also as context management tool. If using for context management, it's reasonable to interpret "code" as "internal code used by claude to support its work", not "my work".

The command should telegraph the consequences & meaning of the dangerous operations more clearly, ask for confirmation before proceeding, ideally confirm the blast radius, and preferably start with the "safe" default of "chat only".

Environment Info

  • Platform: darwin
  • Terminal: Apple_Terminal
  • Version: 2.1.114
  • Feedback ID: 1da591a2-5c87-4325-9b8b-906082f67a40

Errors

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/robmorris/.local/share/claude/versions/2.1.114 (expected in multi-process scenarios)\n    at sd_ (/$bunfs/root/src/entrypoints/cli.js:2751:2177)\n    at WH8 (/$bunfs/root/src/entrypoints/cli.js:2751:1257)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-19T20:53:14.148Z"}]

View original on GitHub ↗

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