[Bug] Previous session becomes unresponsive when opening new session in same project

Bug Description
When opening a new Claude Code session in the same project, the previous session becomes unresponsive. Claude gets stuck processing, and after pressing escape, any new commands typed are not acknowledged. The prompt shows as > with a dark grey background, but Claude does not respond to any input.

Steps to Reproduce

1. Start a Claude Code session in a project directory
2. Open a second Claude Code session in the same project directory
3. The first session gets stuck processing
4. Press escape to stop processing
5. Type any command in the first session
6. The command is not acknowledged - session is completely unresponsive

Expected Behavior
Either:

• Both sessions should remain active and responsive, OR
• Clear documentation/warning about single-session limitation, OR
• Graceful handling with a message explaining the session is inactive

Actual Behavior
The previous session silently becomes unresponsive with no indication of why commands are being ignored.

Environment Info

• Platform: linux
• Terminal: (using in remote environment)
• Version: 2.0.45
• OS: Linux 5.15.0-157-generic

Additional Context
This behavior was not present in earlier versions - users report this as new/changed behavior. There is no documented configuration to allow multiple active sessions or to control this behavior.

Errors

[]