Skip to content

[Bug] Multiple Claude Code instances fail after update to 2.0.60 #13280

Closed as not planned

Description

@mariusmcl

Bug Description
hey. after updating to 2.0.60, i can no longer run multiple instances of CC in the cursor terminals.

Environment Info

  • Platform: darwin
  • Terminal: cursor
  • Version: 2.0.60
  • Feedback ID: b34bf1b9-1c8f-4a96-a977-132708c282a7

Errors

[]

Activity

  1. DavidPluxia commented on Dec 7, 2025

    @DavidPluxia

    Having the same issue. Anything above 3 CC instances starts hanging

  2. 10eputzen commented on Dec 7, 2025

    @10eputzen

    My WSL with Ubuntu can't even handle more than 1 instance ... but downgrading to 2.58 did not help either so it must be something server-side.

  3. sebmack commented on Dec 7, 2025

    @sebmack

    Same issue on VS Code terminals. Used to run 3/4 terminals happily until it did the weird endless-scrolling thing. Now it crashes soon as I go above 1 instance. Opus 4.5.

  4. 10eputzen commented on Dec 7, 2025

    @10eputzen

    Fixed with 2.61.0 - Thank God other people are also working on a Sunday!

  5. phuochau commented on Dec 7, 2025

    @phuochau

    2.0.61 stills not working

  6. 10eputzen commented on Dec 7, 2025

    @10eputzen

    true, guess I just got lucky with my first two sessions in 2.0.61

  7. phuochau commented on Dec 7, 2025

    @phuochau

    there is a tip: use Claude Code VS Extension, it will work but still like the cli experience

  8. cyreb7 commented on Dec 8, 2025

    @cyreb7

    Same issue in VS Code terminal via WSL on 2.0.61. More than one instance does not work

  9. github-actions commented on Jan 8, 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.

  10. github-actions commented on Feb 9, 2026

    @github-actions

    This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.

  11. github-actions commented on Feb 16, 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.

  12. locked as resolved and limited conversation to collaborators on Feb 16, 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

    autocloseIssue will be closed automatically

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions