Skip to content

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

Closed

Description

@smconner

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?

Platform: Linux (Ubuntu 24.04)

Description: After upgrading to 2.0.60, both resumed and fresh conversations randomly become completely unresponsive. The prompt appears active but accepts no input. No error message is displayed.

Symptoms:

  • Prompt silently stops responding to user input
  • ESC does not interrupt - prompt remains dead
  • Some slash commands still work (/context) but others don't
  • User input appears to be queued but not processed

Reproduction Evidence: When I manually logged out of my Anthropic account in a separate terminal session, the stuck session immediately displayed two backlogged prompts with "Invalid API key" errors - proving input was being queued but not processed:

ULTRATHINK Let's test the comment tool more...
⎿ Invalid API key · Please run /login

/end is running…
⎿ Invalid API key · Please run /login

Suspected Cause: The new "background agent support" feature (from 2.0.60 release notes: "Added background agent support. Agents run in the background while you work") may be silently blocking the main input loop while waiting on something. In the above example however the whole conversation was static for at least an hour, until I got the idea to re-log.

Workaround: None found, except to log out of anthropic and back in.

Related but different issues found:

Issue is distinct because:

  1. Silent freeze (no CPU spike)
  2. Specifically on 2.0.60 with new background agent feature
  3. Linux platform
  4. Input queues but doesn't process (proven by the logout test showing backlogged prompts)

What Should Happen?

Prompt stays responsive. Background work shows visual feedback. No silent blocking.

Error Messages/Logs

Steps to Reproduce

  1. Upgrade to Claude Code 2.0.60
  2. Start a session (fresh or resumed - both affected)
  3. Work normally for a while (issue is intermittent)
  4. At some point, the prompt stops responding to input
  5. Try ESC - no effect
  6. Try typing - no response
  7. Some slash commands work (/context) but user prompts do not

To prove input is queued (not dropped):
8. In a separate terminal, run: claude logout
9. The stuck session immediately shows backlogged prompts with "Invalid API key" errors

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.0.60

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

No response

Activity

  1. pweisensee commented on Dec 6, 2025

    @pweisensee

    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

  2. leagueupinc commented on Dec 6, 2025

    @leagueupinc

    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.

  3. danlannan777 commented on Dec 6, 2025

    @danlannan777

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

  4. mostafaibrahim17 commented on Dec 6, 2025

    @mostafaibrahim17

    same thing here

  5. SaitoPhoenix commented on Dec 6, 2025

    @SaitoPhoenix

    Would love to know if this is a bug or intentional

  6. antoineschaller commented on Dec 6, 2025

    @antoineschaller

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

  7. anton-abyzov commented on Dec 6, 2025

    @anton-abyzov

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

  8. mehulparmariitr commented on Dec 6, 2025

    @mehulparmariitr

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

  9. mehulparmariitr commented on Dec 6, 2025

    @mehulparmariitr

    @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.

  10. RonRichman commented on Dec 6, 2025

    @RonRichman

    Likewise

  11. 65 remaining items

  12. JZtesting commented on Dec 8, 2025

    @JZtesting

    I am still getting this issue with 2.0.61.

    make sure you restart all IDEs fixed it for me.

  13. productdevbook commented on Dec 8, 2025

    @productdevbook

    2.0.61 macos same problem +3 terminal.

  14. igorkofman commented on Dec 9, 2025

    @igorkofman
    Collaborator

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

  15. thealbertyang commented on Dec 9, 2025

    @thealbertyang

    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.

  16. skinnyandbald commented on Dec 9, 2025

    @skinnyandbald

    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

  17. weisisheng commented on Dec 10, 2025

    @weisisheng

    Agreed

  18. ltawfik commented on Dec 10, 2025

    @ltawfik
    Collaborator

    please update to version 2.0.62

  19. weisisheng commented on Dec 10, 2025

    @weisisheng

    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.

  20. hackyon-anthropic commented on Dec 10, 2025

    @hackyon-anthropic
    Collaborator

    @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.

  21. lgsf commented on Dec 10, 2025

    @lgsf

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

  22. lgsf commented on Dec 10, 2025

    @lgsf

    This needs to be reopened. It is not fixed

  23. hackyon-anthropic commented on Dec 11, 2025

    @hackyon-anthropic
    Collaborator

    @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.

  24. github-actions commented on Dec 19, 2025

    @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.

  25. locked as resolved and limited conversation to collaborators on Dec 19, 2025
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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions