[BUG] Console freezes when using /rewind immediately after /resume
Status Fixed / completed
Reported on v2.1.118
Maintainer reply ✓ Yes — mhegazy
Workaround ✓ Mentioned in thread ↓
Activity 5 comments · opened Apr 23, 2026 · closed Apr 23, 2026
💡 Likely answer: A maintainer (mhegazy, contributor)
responded on this thread — see the highlighted reply below.
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
When using resume to restore a historical session and then immediately using rewind, the console window freezes and becomes unresponsive. Neither Enter nor Esc works, and I have to forcibly kill the current window. If rewind is executed right after resume, it gets stuck in a pending state. This situation should be handled properly!
Version: v2.1.118
What Should Happen?
can use rewind
Error Messages/Logs
Steps to Reproduce
claude -r- choice a history session
- waiting for load
rewind- freeze!
Claude Model
Other
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.118
Platform
Other
Operating System
Windows
Terminal/Shell
PowerShell
Additional Information
_No response_
5 Comments
Found 1 possible duplicate issue:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
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 have frozen issue despite the fix. The workaround from @PohTeyToe works:
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.