Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Interactive menus (MCP, rewind) completely unresponsive on --resume [5 comments, 6 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#52281•Fetched 2026-04-24 06:11:19
View on GitHub
Comments
5
Participants
6
Timeline
15
Reactions
0
Author
EtienneBBeaulacEtienneBBeaulac
Participants
EtienneBBeaulacEtienneBBeaulacgithub-actions[bot]github-actions[bot]mhegazymhegazymrmemes-ethmrmemes-ethmugur-ripiomugur-ripioPohTeyToePohTeyToe
Timeline (top)
commented ×5labeled ×5cross-referenced ×4closed ×1

Error Message

Error Messages/Logs

Code Example

From claude --resume --debug-file /tmp/debug.txt, the following pattern appears immediately after startup and persists indefinitely:

  [STARTUP] showSetupScreens() completed in 4588ms   ← normal is <100ms
  [DEBUG] High write ratio: blit=0, write=31269 (100.0% writes), screen=477x244
  [DEBUG] High write ratio: blit=0, write=31506 (100.0% writes), screen=487x244
  [DEBUG] High write ratio: blit=0, write=31710 (100.0% writes), screen=488x244

  blit=0, write=100% never normalizes -- the renderer stays in full-redraw mode and never engages the overlay/menu input system.

  Also previously seen (with multiple sessions): Cannot acquire lock for 2.1.118 - held by PID XXXXX -- however the hang reproduces with only a single claude process running, so the lock conflict is not the sole cause.

  Potentially related open issue: #13287
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

When resuming a session with claude --resume, interactive menus (MCP picker /mcp, rewind) render visually but accept no keyboard input whatsoever -- arrow keys, Escape, Enter, and Ctrl-C are all unresponsive. The only recovery is force-killing the terminal window or kill -9 from another tab. Affects both iTerm2 and Terminal.app.

Fresh sessions (claude without --resume) work correctly every time.

What Should Happen?

Interactive menus should respond to keyboard input after --resume, identical to fresh sessions.

Error Messages/Logs

From claude --resume --debug-file /tmp/debug.txt, the following pattern appears immediately after startup and persists indefinitely:

  [STARTUP] showSetupScreens() completed in 4588ms   ← normal is <100ms
  [DEBUG] High write ratio: blit=0, write=31269 (100.0% writes), screen=477x244
  [DEBUG] High write ratio: blit=0, write=31506 (100.0% writes), screen=487x244
  [DEBUG] High write ratio: blit=0, write=31710 (100.0% writes), screen=488x244

  blit=0, write=100% never normalizes -- the renderer stays in full-redraw mode and never engages the overlay/menu input system.

  Also previously seen (with multiple sessions): Cannot acquire lock for 2.1.118 - held by PID XXXXX -- however the hang reproduces with only a single claude process running, so the lock conflict is not the sole cause.

  Potentially related open issue: #13287

Steps to Reproduce

  1. Start claude and have a substantial conversation
  2. Exit
  3. Run claude --resume
  4. Try to open any interactive menu (/mcp, rewind)
  5. Menu renders but is completely frozen -- no key input accepted, including Ctrl-C

My computer crashed a few times, which may have been the trigger for this behavior.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.118 (Claude Code)

Platform

AWS Bedrock

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The issue can be potentially resolved by investigating and addressing the high write ratio and full-redraw mode in the renderer, which may be causing the interactive menus to freeze.

Guidance

  • Investigate the cause of the high write ratio and full-redraw mode in the renderer, as indicated by the debug logs (blit=0, write=100%).
  • Check if the issue is related to the previously seen lock conflict error, although it's noted that the hang reproduces with only a single claude process running.
  • Try to reproduce the issue with a different terminal or shell to see if it's specific to Terminal.app.
  • Review the potentially related open issue #13287 to see if it provides any insights or solutions.

Example

No code snippet is provided as it's not clearly supported by the issue.

Notes

The issue may be related to a regression, but the last working version is not specified. The computer crashes may have triggered the behavior, but it's unclear if it's a contributing factor.

Recommendation

Apply workaround: Investigate and address the high write ratio and full-redraw mode in the renderer, as it's the most likely cause of the issue. This may involve modifying the rendering logic or adjusting the debug settings to better understand 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…
#retrieval issue#search optimization#API routing#API middleware#SSR setup

Still need to ship something?

×6

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

Back to top recommendations

TRENDING