[Bug] Rewind functionality causes terminal freeze, unable to exit or navigate
Resolved 💬 18 comments Opened Apr 23, 2026 by byronluk Closed Apr 23, 2026
💡 Likely answer: A maintainer (mhegazy, contributor)
responded on this thread — see the highlighted reply below.
Bug Description
This claude session has broke somehow and I can no longer rewind. Once I try rewinding, I get stuck in the rewind screen. I can't exit back out, nor can I move to past messages. I'm just stuck. I have to kill my terminal window entirely. I can't even ctrl+C out.
Environment Info
- Platform: darwin
- Terminal: Superset
- Version: 2.1.118
- Feedback ID: 4b0211a7-a518-4a90-a3e5-97ef3afcf0b1
Errors
[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/byronluk/.local/share/claude/versions/2.1.118 (expected in multi-process scenarios)\n at ai_ (/$bunfs/root/src/entrypoints/cli.js:2756:2177)\n at IK8 (/$bunfs/root/src/entrypoints/cli.js:2756:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T01:05:31.523Z"}]
18 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Adding another data point — same freeze, different terminal:
claude --resume <session>then/rewind— picker renders but is completely unresponsive.Esc Escbehaves identically (same frozen picker).killfrom another terminal works; Ctrl+C has no effect.Consistent with #52329, #52268, #52281, #52319 — looks like a cross-platform 2.1.118 regression in the rewind picker's input handling on resumed sessions.
Adding a launch-path bisection from my repro (Windows 10, VS Code integrated terminal, CC 2.1.118, bash/Git Bash):
| Launch method | Rewind behavior |
|-|-|
|
claude→/resume(picker from inside TUI) | Works ||
claude --resume <session-id>(explicit id) | Works ||
claude --resume(no id, launch-time picker) | Input deadlocked |Same underlying session file in all three cases. Only the bare-flag launch-time picker path breaks Rewind.
--resume <id>hydrates the session without ever showing the launch-time picker and is fine;/resumefrom inside a running TUI is also fine. So the bug is specific to the--resume-with-launch-picker startup path, which suggests the launch-time picker hydrates the session before the TUI input loop is fully wired and leaves the keypress handler in a bad state that only surfaces once Rewind is opened.Combined with #52329's
CLAUDE_CONFIG_DIRbisection (trigger lives in~/.claude.json, not session-history size), this narrows the repro further: it's the launch-picker path reading~/.claude.jsonstate during session hydration.Workaround until fixed: resume with an explicit id (
claude --resume <session-id>) or launch bareclaudeand use/resumefrom inside. Skip the bare--resumepicker.Thanks for reporting. Fix should be in tomorrows release.
still not fixed for me
https://github.com/anthropics/claude-code/issues/53011
@mhegazy so where is the fix??? It's still broken...
still not fixed.
Workaround found for /rewind freeze on Windows (v2.1.119)
Bug trigger: Starting a session with claude -r / claude --resume causes /rewind (or double ESC) to freeze completely.
Workaround:
Start fresh with claude (no flags)
Use /resume inside the session to select and re-enter the previous session
/rewind works normally from there
Same session resumption, but the entry method makes the difference. This appears to be a regression of the previously fixed bug: "/rewind and other interactive overlays not responding to keyboard input after launching with claude --resume"
Tested on: Windows, Git Bash & PowerShell, session file under 10MB, v2.1.119
@KKingdong unfortunately does not help on macOS
new version released. try this one.
you have to update using npm ('claude update' still stays in v2.1.119): npm install -g @anthropic-ai/claude-code@2.1.120
(and uninstall v2.1.119)
https://www.npmjs.com/package/@anthropic-ai/claude-code/v/2.1.120
I installed Claude code like this
curl -fsSL https://claude.ai/install.sh | bash
On Mon, 27 Apr 2026 at 12:27 PM KKingdong @.***> wrote:
Appologies. i miss spoke. the fix is in 2.1.120, should be release shortelly
i dont know if this is similar to the other bug where you cannot launch claude at all and it locks the terminal, but that is not fixed in 2.1.120.
@nmorgowicz please file a new issue
Had this issue using Claude Code inside a Docker container. It seems like this problem is fixed, thanks!
Wow Had this issue and updating the version fixed it
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.