[Bug] VSCode Plugin 2.1.39 hangs after first request

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/24484
2. https://github.com/anthropics/claude-code/issues/17667
3. https://github.com/anthropics/claude-code/issues/17926

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

you mean this? … (4m 40s · ↑ 0 tokens)

Yes, ok I think I figured out something. If the first question is too complicated it will hang. If you first ask something simple it seems to work. Very strange but I just created this hang 5 times, was able to do it in claude-code terminal with no problems. Now I restarted vscode and asked something simple and it works. It seems to be some kind of timing problems. If you cancel the output of the first message because you forgot something it gets even worse. I bet you it has something to do with capturing the first sessionId tagged on the output of the first message from the claude-agent-sdk.

I think it’s intentional because the /fast feature might get more interesting that way. In the end, it’s economically the most reasonable choice to delay the response for most users. It’s pretty obvious.

Edit: I noticed it shortly before the /fast feature and 4.6, it’s just working as planned:
https://github.com/anthropics/claude-code/issues/22855

I am not sure if it has anything to do with a desired feature. About 1/2 of the time I have to close and restart vscode now to get it to work. Once there is at least one message in the thread it will work, but to get the first message in there is haphazard today. It just ends up ideating.... forever and never proceeds to answer. This is not an issue talking to the same agent using the terminal cli. So I think it's an initialization problem. Existing threads also work fine, because there are messages in there already.

I also noticed that the /mcp command no longer works correctly. When it says "Continue in Terminal" it never opens the terminal but waits. Not sure if it has anything to do with the OS, but it's just not working on 11 today.

Have you tried different models and different levels on Opus? Huge difference on Opus level 3

But once it works then it keeps on working. It doesn't seem to be specific to the model or settings. It feels like the last version of the extension no longer properly initializes. It can't open the terminal window anymore and sometimes I can't open the side bar or side panel either. Restarting doesn't fix it and sometimes I even have Claude processes stuck I need to kill manually. Something is not 100% right. Since the terminal client works fine it feels like it's something with the plugin only

Fixed in 2.1.41 for me.

@richtera

https://github.com/anthropics/claude-code/releases/tag/v2.1.41

Fixed AWS auth refresh hanging indefinitely by adding a 3-minute timeout

I hope so.

The 2.1.41 completely fixes the problem, the initialization is now correct, I can open up the terminal again and send the first message on a new thread without having to worry. Thank you!

Bonjour, bloqué depuis 3 jours sur windows 11
Extension VS Code ne répond pas - bloquée sur « Forging/Cooking/Pondering
Une solution svp?

@misterjohn03100 I found the last version 2.1.41 worked fine. I think I should close this one since I have used claude code all day without issue after upgrading to 2.1.41, maybe windows has a different issue.

Merci pour ton retour. En rallument simplement le pc, tout est revenu à la normale. Pas compris mais tant mieux.

This maybe back.
2.1.42 is hanging for me again.

Yes it's reproducibly broken. Going back to terminal again, please repair.

Haha CAT AND MOUSE.
2.1.44 works again.

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.