claude --resume hangs uninterruptibly when no conversations found
Status Fixed / completed
Maintainer reply ✓ Yes — blois
Activity 5 comments · opened Mar 5, 2026 · closed Mar 5, 2026
💡 Likely answer: A maintainer (blois, collaborator)
responded on this thread — see the highlighted reply below.
Description
When running claude --resume and no previous conversations exist, the process displays "No conversations found to resume" but then enters a hung state that does not respond to terminal signals.
Steps to Reproduce
- Run
claude --resumein a state where no previous conversations exist - Observe the message: "No conversations found to resume. Press Ctrl+C to exit and start a new conversation."
- Press Ctrl+C - nothing happens
- Press Ctrl+\ (SIGQUIT) - nothing happens
- Process can only be terminated via external
killsignal
Expected Behavior
- Ctrl+C should exit the process cleanly, OR
- The process should exit automatically after displaying the "no conversations found" message
Environment
- OS: Fedora Linux (6.18.13-200.fc43.x86_64)
- Terminal: SSH session (AbsoluteTelnet client from Windows)
Related Enhancement
Exposing Claude Code's own PID to the model would help users safely identify which process to kill when running multiple sessions. Currently, users cannot ask "what is your PID?" to avoid accidentally terminating an active session.
5 Comments
Found 1 possible duplicate issue:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
What
claudeversion is this on? There were some issues around here that were fixed with2.1.21.Version 2.1.19. I'll update to 2.1.21+ and retest.
Confirmed fixed in 2.1.69. Ctrl+C now works as expected.
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.