claude --resume hangs uninterruptibly when no conversations found

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

1. Run claude --resume in a state where no previous conversations exist
2. Observe the message: "No conversations found to resume. Press Ctrl+C to exit and start a new conversation."
3. Press Ctrl+C - nothing happens
4. Press Ctrl+\ (SIGQUIT) - nothing happens
5. Process can only be terminated via external kill signal

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.