claude-code - 💡(How to fix) Fix [BUG] /rewind causes complete terminal lockup on any --resume'd session — Ctrl+C does not work [3 comments, 4 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52329Fetched 2026-04-24 06:10:03
View on GitHub
Comments
3
Participants
4
Timeline
15
Reactions
4
Author
Timeline (top)
cross-referenced ×7commented ×3labeled ×3closed ×1

Root Cause

Appears closely related to / possibly same root cause as:

  • #52281 — Interactive menus (MCP, rewind) completely unresponsive on --resume (macOS, 2.1.118)
  • #52268 — Console freezes when using /rewind immediately after /resume (Windows, 2.1.118)
  • #52319 — /rewind interactive picker stops accepting keyboard input in 2.1.118 (Linux regression from 2.1.117)
  • #52209 — Rewind functionality causes terminal freeze (macOS, 2.1.118)
RAW_BUFFERClick to expand / collapse

What's wrong

On any claude --resume'd session, invoking /rewind (or Esc Esc) opens the rewind picker but it is completely unresponsive to keyboard input. Esc, Enter, and arrow keys do nothing. Ctrl+C also does not work — the session is a hard lockup. The only way to recover is Ctrl+Z to suspend, then kill %1.

Verified working correctly on 2.1.116. Broken on 2.1.118.

Repro

  1. claude --resume <any session> (reproducible on an absolute clean repo with minimal history — not session-specific)
  2. Type /rewind (or press Esc Esc)
  3. Picker renders, but no keys reach it. Ctrl+C doesn't kill the session either.
  4. Recovery: Ctrl+Z, then kill %1

Scope

  • Only reproducible after --resume. Fresh claude sessions handle /rewind correctly.
  • Reproducible in every resumed session, not specific to one.
  • Reproducible with a minimal ~/.claude.json copied to a throwaway CLAUDE_CONFIG_DIR, so it's not session-history bloat.
  • Not reproducible with an empty CLAUDE_CONFIG_DIR. Something in ~/.claude.json state is the trigger.

Environment

  • Claude Code: 2.1.118 (confirmed working on 2.1.116)
  • OS: macOS
  • Terminal: Ghostty (also reproduces in Terminal.app — not terminal-specific)
  • TERM=xterm-256color
  • tmux: not involved
  • Vim mode: off
  • No ~/.claude/keybindings.json

What I tried

  • Disabled vim mode: no change
  • Switched to Terminal.app: no change
  • Killed all stale Claude Code processes and restarted terminal: no change
  • Clean CLAUDE_CONFIG_DIR: works correctly. Problem reappears when ~/.claude.json is in place.
  • Problem does not depend on session history size — reproducible with near-empty history.

Expected

/rewind picker responds to Esc / Enter / arrows. At minimum, Ctrl+C should always kill the session.

Related issues

Appears closely related to / possibly same root cause as:

  • #52281 — Interactive menus (MCP, rewind) completely unresponsive on --resume (macOS, 2.1.118)
  • #52268 — Console freezes when using /rewind immediately after /resume (Windows, 2.1.118)
  • #52319 — /rewind interactive picker stops accepting keyboard input in 2.1.118 (Linux regression from 2.1.117)
  • #52209 — Rewind functionality causes terminal freeze (macOS, 2.1.118)

This report adds the CLAUDE_CONFIG_DIR bisection data point: the trigger lives in ~/.claude.json contents, not in session-history size or the session file itself.

extent analysis

TL;DR

The issue can be temporarily worked around by using an empty CLAUDE_CONFIG_DIR or downgrading to version 2.1.116.

Guidance

  • The problem seems to be triggered by something in the ~/.claude.json file, as an empty CLAUDE_CONFIG_DIR resolves the issue.
  • Try removing or renaming the ~/.claude.json file to see if the issue persists.
  • Since the issue is reproducible on multiple platforms and terminals, it's likely a Claude Code issue rather than a terminal or OS problem.
  • Given the related issues, it's possible that this is a regression introduced in version 2.1.118.

Example

No code snippet is provided as this issue appears to be related to configuration and versioning rather than code.

Notes

The exact cause of the issue is still unknown, but it seems to be related to the ~/.claude.json file and the version of Claude Code being used.

Recommendation

Apply workaround: Use an empty CLAUDE_CONFIG_DIR or downgrade to version 2.1.116, as these have been confirmed to resolve the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] /rewind causes complete terminal lockup on any --resume'd session — Ctrl+C does not work [3 comments, 4 participants]