Repository navigation
[BUG] CRITICAL: Multiple Instances of Claude Code now prevent each other from working #13499
Description
Preflight Checklist
- I have searched existing issues and this hasn't been reported yet
- This is a single bug report (please file separate reports for different bugs)
- I am using the latest version of Claude Code
What's Wrong?
For some reason in 2.0.61, if I load two Claude code instances, they can no longer operate in parallel. Now when one runs, the other one stops and no more messages can be received by the other instance. This is a huge regression.
What Should Happen?
Multiple instances of cluade code should be able to run in parallel without interfering with each other
Error Messages/Logs
NoneSteps to Reproduce
- Open two instances of claude code.
- Send a prompt in to one
- Wati until its running
- Send a prompt into the other instnace
- Watch as the first instance halts and cannot proceed.
- Observe the new messages to the first instance will not go through
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.0.50
Claude Code Version
2.0.61
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
This is a HUGE issue, please look to fix immediately. I like to be able to run multiple instances in parallel for my workflow
Reacted by Pierre, Tim Robinson and saadfaruque99
Activity
github-actions commentedon Dec 9, 2025
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
khari998 commentedon Dec 9, 2025
This is not a duplicate because I dont get the errors mentioned in the previous tickets. instead the instances just stop mid generation and further messages are never recognized
blois commentedon Dec 10, 2025
Is this in the VSCode terminal? If so,
2.0.61should have the fix, but the window may need to be reloaded for the extension to be updated for it.github-actions commentedon Dec 20, 2025
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.