Skip to content

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

Closed as not planned

Description

@paulpreibisch

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

[]

Activity

  1. github-actions commented on Jan 6, 2026

    @github-actions

    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.

  2. atani commented on Feb 6, 2026

    @atani

    Still occurring on the latest version.

    • Claude Code version: 2.1.33
    • OS: macOS (Darwin 25.2.0)
    • Architecture: arm64 (Apple Silicon)
    ERROR  undefined is not an object (evaluating 'U.length')
    
     /$bunfs/root/claude:668:20555
    
     - O7 (/$bunfs/root/claude:668:20555)
     - RX (/$bunfs/root/claude:668:28704)
     - rO (/$bunfs/root/claude:668:28858)
     - M7 (/$bunfs/root/claude:668:25070)
    

    Stack trace differs slightly from #20685 due to version/build difference, but same root cause (React hook dependency array becomes undefined).

  3. github-actions commented on Mar 6, 2026

    @github-actions

    Closing for now — inactive for too long. Please open a new issue if this is still relevant.

  4. github-actions commented on Mar 13, 2026

    @github-actions

    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.

  5. locked as resolved and limited conversation to collaborators on Mar 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:corebugSomething isn't workinghas reproHas detailed reproduction stepsplatform:linuxIssue specifically occurs on LinuxstaleIssue is inactive

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions