claude doctor freezes at 'Press Enter to continue...' - Enter key unresponsive (v2.1.17)
Resolved 💬 6 comments Opened Jan 23, 2026 by srs-adamr Closed Jan 23, 2026
Description
After running claude doctor or claude -r (resume with no conversations), the terminal freezes at prompts and becomes completely unresponsive. Keyboard input is not registered.
Environment
Claude Code
- Version: 2.1.17 (latest channel)
- Install method: native
- Path:
~/.local/share/claude/versions/2.1.17
System
- Model: MacBook Pro (Mac16,7)
- Chip: Apple M4 Pro (14 cores: 10 performance + 4 efficiency)
- Memory: 48 GB
- OS: macOS 26.2 (25C56)
- Kernel: Darwin 25.2.0
Runtime
- Node.js: v25.1.0
- npm: 11.6.2
Steps to Reproduce
Scenario 1: claude doctor
- Run
claude doctor - Wait for diagnostics to complete
- See "Press Enter to continue..." prompt
- Press Enter - nothing happens, terminal is frozen
Scenario 2: claude -r with no conversations
- Run
claude -rin a directory with no previous conversations - See "No conversations found to resume." and "Press Ctrl+C to exit and start a new conversation."
- Press Ctrl+C - nothing happens, terminal is frozen
Expected Behavior
- Enter should dismiss the "Press Enter to continue..." prompt
- Ctrl+C should exit and start a new conversation
Actual Behavior
The terminal freezes and all keyboard input is ignored. Ctrl+C does not work - the process must be forcibly killed with pkill claude or similar.
Diagnostics Output (Scenario 1)
Diagnostics
├ Currently running: native (2.1.17)
├ Path: ~/.local/share/claude/versions/2.1.17
├ Invoked: ~/.local/share/claude/versions/2.1.17
├ Config install method: native
└ Search: OK (bundled)
Updates
├ Auto-updates: enabled
├ Auto-update channel: latest
├ Stable version: 2.1.7
└ Latest version: 2.1.17
Version Locks
└ No active version locks
Press Enter to continue...
Resume Output (Scenario 2)
No conversations found to resume.
Press Ctrl+C to exit and start a new conversation.
Additional Context
This issue started occurring after the recent update to version 2.1.17.
This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗