You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug] Previous session becomes unresponsive when opening new session in same project #13268
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
Start a Claude Code session in a project directory
Open a second Claude Code session in the same project directory
The first session gets stuck processing
Press escape to stop processing
Type any command in the first session
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
[]
Reacted by Vince Fulco--MarginLevers.com, Mark Vasilyev, Abhishek, strangevaleera, TommyTommy1234, sebmack, Michael Honsel, saadfaruque99 and mstfkrdnz
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
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.
Activity
github-actions commentedon Jan 6, 2026
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
atani commentedon Feb 6, 2026
Still occurring on the latest version.
Stack trace differs slightly from #20685 due to version/build difference, but same root cause (React hook dependency array becomes undefined).
github-actions commentedon Mar 6, 2026
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
github-actions commentedon Mar 13, 2026
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.