[BUG] Sessions become unresponsive after upgrade to 2.0.60 (suspected background agent blocking)

I started getting the same thing, immediately after getting the update to this version. I also use multiple terminals running claude code at once, so maybe that is a contributing factor? they seem to become unresponsive very quickly, a few messages in sometimes.

I'm on MacOS 15.7.2

Experiencing the same here. No sub-agents, but when 1+ Claude Code CLI is established in IDE, all but one silently hang with no resolution but to close and restart chat, but then within minutes all fail but just one.

Also running into this since 2.0.60. Was not happening until the upgrade

same thing here

Would love to know if this is a bug or intentional

Same here, even tried rolling back to 2.0.59 and it does not solve the issue :(

I experience the same problem, I got it in 2.0.57 version too yesterday, it's all the same freezing in 57 & 60!

I am on 2.0.59, happening for me as well!!

@smconner Is it just unresponsive or the speed is also affected while thinking? For me coding work is going very slow even on Sonnet 4.5.

Likewise

also having this issue, anyone see if there is a version we can roll back to that fixes?

This is happening in all versions, I am on 2.0.54, and it is happening on max plan.
To be honest, this looks like more blocking us from using multiple terminals with claude at once...

Yeah it's completely broken now. Nothing works at all. It has become competently fucked up. All sessions hangs in an unrecoverable state after 1-3 minutes

This is happening in all versions, I am on 2.0.54, and it is happening on max plan. To be honest, this looks like more blocking us from using multiple terminals with claude at once...

Interesting hypothesis. That would be a deal breaker if true.

Yeah it's completely broken now. Nothing works at all. It has become competently fucked up. All sessions hangs in an unrecoverable state after 1-3 minutes

If you have a session going, and you open and run claude. Boom, your current session is gone. Very weird...

> This is happening in all versions, I am on 2.0.54, and it is happening on max plan. To be honest, this looks like more blocking us from using multiple terminals with claude at once... Interesting hypothesis. That would be a deal breaker if true.

Totally, but at this point any shady tactics I can expect from Anthropic

This is getting a bit ridiculous. Work is grinding to a halt, claude code is highly degraded.

As a temporary measure.. i tried using vscode extension to do my parallel work instead and so far is working fine in v2.0.60.

I started getting this this morning, did some debugging to figure out it was the new version, dialed it back to Claude Code v2.0.55, and I'm still seeing the issue.

Making this system, I developed that's freaking amazing, absolute garbage! Anyone know a stable version?

I see someone writing that they got this working using VS Code, so I should confirm that I'm on cursor over WSL running or was running multiple sessions out of the same project with hooks to make sure the right responses went to the right sessions.

And I've seen folks say that 59, 58, and 57, are all problematic and I'm saying 55 is as well...Does seem to work fine single threaded but I intentionally wrote a lot of code to let it support multi-threaded so I could have seven different processes running or so.

Does anybody have a known version of cc that works multi-threaded, since down to 55 seems broken?

I've built a kind of neat research tool as part of this and lots of ideas answers in here I'm too tired to try them and hopefully anthropic fixes stuff But tomorrow I'll try 2.0.51 per this: https://reports.perceptionbuilder.com/geek/claude-code-version-stability-rollback_20251206.html

Quick note: cleaning ~/.claude subdirs as laid out in the doc above did not help me recover from .60 back to .55 so I will try .51 later.

How the heck does this get past all QA and internal Anthropic employees / users into the wild? I noticed this started about 14 hours ago, after a full day of successful building / refactoring.

This bug is REALLY making me think about turning off automatic updates.

On Sun, Dec 7, 2025 at 8:14 AM hookey13 @.***> wrote:

hookey13 left a comment (anthropics/claude-code#13188) <https://github.com/anthropics/claude-code/issues/13188#issuecomment-3621451646> Experiencing the same issue on macOS with Claude Max. My debugging findings: Simple prompts work fine (e.g. "Hey, what's 2+2?" responds in 2 seconds) Workflows/slash commands that read multiple files hang indefinitely Tested with --dangerously-skip-permissions, --debug, and plain claude - all hang Network is confirmed fine (5ms ping to api.anthropic.com, no packet loss) API status shows all systems operational Timeline: Started immediately after auto-update to 2.0.60 on Dec 6 Confirming the multi-terminal theory: I had multiple Claude Code terminals open when this started. The terminals running workflows that load multiple config files all hung at the loading animation ("Photosynthesizing...", "Flowing...", "Boondoggling..."), while a simple slash command in a fresh single terminal worked. This is a significant regression that's blocking real work. I've also opened #13254 <https://github.com/anthropics/claude-code/issues/13254> with detailed reproduction steps. Anthropic - this needs urgent attention. Multiple users across macOS, Linux, and Windows are all dead in the water. — Reply to this email directly, view it on GitHub <https://github.com/anthropics/claude-code/issues/13188#issuecomment-3621451646>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABWQMFOVAOXBLQ3CYBXMGT4AN5OXAVCNFSM6AAAAACOHD3VQCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMRRGQ2TCNRUGY> . You are receiving this because you were mentioned.Message ID: @.***>

I switched to Sonnet using the /model toggle and it seems to be running more consistently.

Edit: I lied. Seems after 10-15 minutes of use, the "hanging" effect re-surfaces.

I'm experiencing a similar issue with a specific, reproducible trigger: opening a second Claude Code session in the same project directory.

Steps to Reproduce:

1. Start Claude Code session in a project directory
2. Open a second Claude Code session in the same project directory
3. First session immediately gets stuck processing
4. Press escape - session shows > prompt with dark grey background
5. Any command typed is completely ignored - no response from Claude

Environment:

• Platform: Linux 5.15.0-157-generic
• Version: 2.0.45

Key difference from main issue: The trigger is consistent and reproducible - it happens immediately when opening a second session in the same project, rather than randomly during normal use.

This suggests the background agent blocking may be specifically triggered by session conflicts when multiple instances run in the same directory.

Related issue filed: #13268

Hey all, looking

@bcherny works now

We pushed out a configuration change at 10:49:50 PM (~1 hour 44 mins ago). For those of you who have been affected by this issue, do you still see it now? It seems like the issue is resolved for @thealbertyang and @weisisheng ?

Question: is anyone hitting this issue NOT using a terminal in an IDE?

We pushed out a configuration change at 10:49:50 PM (~1 hour 44 mins ago). For those of you who have been affected by this issue, do you still see it now? It seems like the issue is resolved for @thealbertyang and @weisisheng ?

Still same, just a screenshot of how the terminal behaves when it is stucked.

<img width="509" height="435" alt="Image" src="https://github.com/user-attachments/assets/3e412387-69a4-4872-a944-07037d97869f" />

Basically the first terminal will become unresponsive (not doing anything, adding further prompts will show like the screenshot above) after the 2nd terminal is spawn. Both terminal are pointing at the same directory.

To reproduce,

1. Open first terminal run claude, prompt it to do something
2. Open second terminal as the first terminal is still running, prompt it to do something, on the same directory.
3. First terminal will be unresponsive as shown in the screenshot.

Both are at version 2.60.0

@csh-helixbyte are you running the terminal within an IDE (e.g. vscode, cursor, etc.)? Did you restart the session recently?

@csh-helixbyte are you running the terminal within an IDE (e.g. vscode, cursor, etc.)?

Nope, i am using a warp running on macOS, not within an IDE. Hope this helps.

@csh-helixbyte are you running the terminal within an IDE (e.g. vscode, cursor, etc.)? Did you restart the session recently?

Same issue in cursor IDE

Not sure if this helps, but as i do this withn vscode using the claude code extension, it works fine in parallel. Was working with this the whole day today.

<img width="807" height="974" alt="Image" src="https://github.com/user-attachments/assets/c606e193-d630-4737-9712-6e0071c99161" />

Hmm, error remains for me, two terminals open, start a task on one, then the other one started and pauses. 2.60.0 on ubuntu 24.04, vs code version 1.106.3. Restarted IDE.

Interrupt then >continue doesn't produce a response.

@dicksontsai @bcherny I can confirm that the issue is unchanged as of 5 mins ago. I re-tested using both existing conversations through /resume and with new conversations. Out of 5 open terminal tabs 4 are now frozen in place / stalled (or whatever we're calling the phenomenon). I think the fastest way to get it to the failure state is through using ULTRATHINK.

@dicksontsai @bcherny I can confirm that the issue is unchanged as of 5 mins ago. I re-tested using both existing conversations through /resume and with new conversations. Out of 5 open terminal tabs 4 are now frozen in place / stalled (or whatever we're calling the phenomenon). I think the fastest way to get it to the failure state is through using ULTRATHINK.

can confirm

At this point, we're fairly certain that this issue has to do with the Claude Code for VS Code extension and the usage of terminals within VS Code (Cursor, or other IDE).

Until we release the patch (likely as v2.0.61), I recommend using the CLI directly through a terminal app like iTerm2, etc., which through my personal testing does not get stuck.

At this point, we're fairly certain that this issue has to do with the Claude Code for VS Code extension and the usage of terminals within VS Code (Cursor, or other IDE). Until we release the patch (likely as v2.0.61), I recommend using the CLI directly through a terminal app like iTerm2, etc., which through my personal testing does not get stuck.

even resuming a stuck conversation - in a fresh CC instance direct from CLI - produced from an instance of CC CLI running in the IDE hangs

Hmm... very interesting. iTerm2 Build 3.6.6. With 3 tabs open to remote server, ULTRATHINK on all. Two of them seemingly frozen for 2-3 mins then inexplicably (no input from me) just came back to life and at least one of them finished. Then other came back to life and then froze again, and hasn't finished yet... but I have hope. Oh as I'm typing this the second finished the third never got bogged down / frozen and I'm confident will finish. SO make of that what you will. Not the full bug but not typical behavior either.

same problem, start when 2.0.60 installed, always waiting and no token change, I try to install 2.0.59 or lower version, but this problem still exists

In older versions, after 2.0.60 passes, everything freezes and I can't work anymore.

At this point, we're fairly certain that this issue has to do with the Claude Code for VS Code extension and the usage of terminals within VS Code (Cursor, or other IDE). Until we release the patch (likely as v2.0.61), I recommend using the CLI directly through a terminal app like iTerm2, etc., which through my personal testing does not get stuck.

Fwiw I was working entirely in terminal yesterday (iTerm) so I don't think its the extension. I'll collect more data today though to be sure

@smaccoun do u also use cursor or VSCode? if this is reproducing for you, can you please let us know whether you are connected to the IDE through /ide?

If this is happening to you, can you please try to tell us the output of /ide and let us know if you have multiple terminals connected to VSCode or Cursor at the same time?

If so, can you please restart VSCode/Cursor (exit completely then start it again) and see if the issue still persists?

@smaccoun do u also use cursor or VSCode? if this is reproducing for you, can you please let us know whether you are connected to the IDE through /ide?

I use both. Almost always have VSCode open just for quick git commits and occasional small edits. Almost never use the cc extension. Yesterday i think I had cursor open but never used it. That said yesterday I did

1. At some point I did run one query in the claude code vscode extension just to play around with it since I hadn't used it in a while. I don't remember exactly what I did

1. I used the claude desktop app. I also wanted to try doing the local (not cloud) version that auto starts a worktree. I tried this a few times and did use the little button that allows you to carry the session over to the terminal.

I have no idea when the problem started. If it started after doing this or before. I will try and get more data today

If this is happening to you, can you please try to tell us the output of /ide and let us know if you have multiple terminals connected to VSCode or Cursor at the same time?

If so, can you please restart VSCode/Cursor (exit completely then start it again) and see if the issue still persists?

Here's my /ide output

<img width="1404" height="227" alt="Image" src="https://github.com/user-attachments/assets/3f81e346-5b1d-4865-bdea-2d2acd991795" />

I closed cursor and vscode. I will monitor and get back if I see this issue!

Thanks @smaccoun!

Also, for those who are experiencing this issue:

If you are on v2.0.60, we recommend that you update to our latest hotfix release v2.0.61 from last night and the issue should be alleviated.

If you are still seeing the issue (including those who see it as far back as v2.0.56), then we recommend that you try restarting your VSCode and/or Cursor (exit completely, and restart it again).

Sorry for the inconvenience!

The error/problem is still present for me, updated to v2.0.61, restarted VSCode (I tried multiple times).

I only have one terminal open because I noticed the error occurred, especially when I had more than one Claude Code terminal open at the same time. Now it doesn't even work with just one terminal.

Platform: Linux (Ubuntu 22.04.5 LTS)

@AutismLLM - when you say that it doesn't even work with just one terminal, can you let me know what that means? is it freezing, are the prompts not showing up, or does it crash when you start it?

Yes the same for me for the last two days. Have to restart claude entirely and it still hangs. Assume this will be fixed very soon.

hey @DarrenJCoxon can you please run claude --version and share what version you're on? Is this showing up when you have multiple instances running, or just a single instance? Are you connected to the VSCode/Cursor (run /ide to see)?

hey @DarrenJCoxon can you please run claude --version and share what version you're on? Is this showing up when you have multiple instances running, or just a single instance? Are you connected to the VSCode/Cursor (run /ide to see)?

I was on 2.0.60 but saw your comment above so just updated to 2.0.61 - will see if that fixes the problem.

Looks bug is fixed to me (after upgrading to 2.0.61 and restarting all cursor windows), after a couple of hours of use. Thank you!

Looks bug is fixed to me (after upgrading to 2.0.61 and restarting all cursor windows), after a couple of hours of use. Thank you!

Thanks, @gongx030! You didn't have to reset any cache or anything right you just upgraded? If you happen to have the command that you use to upgrade Claude to the right version would love to see it otherwise I'll just look it up too.

I will do this tonight (In about 5 hours) And report back... fingers crosssed!

@logichammer Nothing else, just upgrade and restart IDE. The issue was getting pretty serious yesterday but now is completely normal.

And i am using

  - Kernel: 6.1.153-175.280.amzn2023.x86_64
  - Architecture: x86_64 (64-bit)

@logichammer Nothing else, just upgrade and restart IDE. The issue was getting pretty serious yesterday but now is completely normal. And i am using `` - Kernel: 6.1.153-175.280.amzn2023.x86_64 - Architecture: x86_64 (64-bit) ``

Perfect...Didn't realize the patch was a full upgrade that went out to everyone...anxious to try and thanks!

@bcherny, @hackyon-anthropic, @gongx030 --

Couldn't wait! Upgrade went perfect and back to running seven to nine sessions flawlessly out of the same project:

<img width="2652" height="568" alt="Image" src="https://github.com/user-attachments/assets/9a895f0b-ccae-4911-991f-3ad2138423bc" />

Thanks for the quick attention and fix!

Works fine here too after the 2.0.61 upgrade. I didn't have auto-update on the vscode extension, so had to manually update that

I have autoupgrade set so have been on 2.0.61 most of today. Have been using for about 6 hours and haven't seen this once!

I haven't fully battle tested with extension and claude desktop app worktrees but this is feeling good so far

I fought this issue for a few hours yesterday. I primarily use VS Code Terminal for Claude Code. This issue was apparent when using the Terminal in VS Code, behaving just as the other reports (the moment you execute a command in a 2nd Terminal window in the same directory, the initial one hangs forever). The VS Code Extension for Claude Code did NOT have the bug. I was able to switch to the VS Code Extension for Claude Code and run multiple Claude Code sessions yesterday while the bug was present in the VS Code Terminal.

I'm still seeing the issue when using VS Code terminal, however, no issues using the mac terminal, so have switched to this.

Update to the latest version and should resolve.

@bcherny @hackyon-anthropic @gongx030 @hackyon-anthropic @dicksontsai (I apologize if I left off any participating collaborators)

I Updated to 2.061 30 mins ago, and I can confirm that the rollback seems to have stabilized things for now.

Since this is rollback and not an actual fix to the affected codebase I'm thinking we should leave this bug report open for now to keep gathering feedback. That said, I think that as your customers / debugging team everyone would benefit from a high-level situation report from your perspective. I'm of the mind that sharing the way you're seeing the issue will help this group of super-users help you fix the bigger issue faster and more effectively.

(I also invite you to share as much detail as you are comfortable with, without posting code snips.)

I am still getting this issue with 2.0.61.

https://github.com/anthropics/claude-code/issues/13188#issuecomment-3625027906 For me as well after about 4 hours of successful usage, the timeouts / hangs surfaced again.

same here, the issue is still there on vs code terminal on 2.0.61

The issue is happening for me more when multiple Claude agents are working on the same Repo. It is able to do multiple agents on multiple repos without any issue

Still happening for me too, even after claude code upgrade

For me it was fixed after upgrading both Claude Code and the Claude Code vscode extensions. For those of you who still has the bug, did you also make sure the vscode extension got upgraded?

For me it was fixed after upgrading both Claude Code and the Claude Code vscode extensions. For those of you who still has the bug, did you also make sure the vscode extension got upgraded?

My vs code is Version: 1.106.3 (Universal), I tried checking for updates it said there are currently no updates available. claude code's version is 2.0.61

Still happening for me in Version: 2.0.61 (on Mac) -- also have multiple tabs in Claude Code sessions

I am still getting this issue with 2.0.61.

make sure you restart all IDEs fixed it for me.

2.0.61 macos same problem +3 terminal.

Is this in VSCode with multiple agent tabs open? If not sounds like a separate issue perhaps / need more info.

We pushed out a configuration change at 10:49:50 PM (~1 hour 44 mins ago). For those of you who have been affected by this issue, do you still see it now? It seems like the issue is resolved for @thealbertyang and @weisisheng ?

Yes, it is still working since the update a few days ago. I am able to run multiple terminals with different sessions on a Mac / VSCode.

Still happening for me on Version: 2.0.62 on MacOS in Claude Code.

Not only is it unresponsive but it seems to think that our conversation is actually the one happening in another terminal session

Agreed

please update to version 2.0.62

please update to version 2.0.62

Updated as soon as it was released, and VS code too. I am now getting timeouts on a single terminal window.

***There are way too many folks seeing the same effects to be able to close this issue prematurely.

@weisisheng sounds like you're running into a different issue entirely, can you file another bug and post a video/screenshot of it? it's unlikely what you're running into is the same issue.

For those who are still seeing this bug beyond v2.0.62, can you please file a bug and assign it to me? I'll do my best to track them down. It'd would be great to actually get a video or screenshots so we can debug what's wrong, otherwise it's really hard for us to help if the reported issue is generic freezing.

if you are still seeing after update, please make sure you do a FULL VSCode restart. It's not enough to just close the current window and reopen, you need to kill VSCode entirely and restart for it to take effect.

Still happening with me. I deleted the entire claude installation. Only on mac os version 2.0.64

This needs to be reopened. It is not fixed

@lgsf you are likely running into another issue, can you file another bug and post a video/screenshot of the issue? Can you also make sure you exit your VSCode entirely and start it again?

For those who are still seeing this bug beyond v2.0.62, can you please file a bug and assign it to me? I'll do my best to track them down. It'd would be great to actually get a video or screenshots so we can debug what's wrong, otherwise it's really hard for us to help if the reported issue is generic freezing.

if you are still seeing after update, please make sure you do a FULL VSCode restart. It's not enough to just close the current window and reopen, you need to kill VSCode entirely and restart for it to take effect.

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.