[BUG] Claude Code VSCode extension is NOT streaming response since 2.1.37
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
There're already multiple posts about this and they're all automatically closed -- since 2.1.37, how is this not something drawing enough attention? Is everyone enjoying the huge dump of response at the very end?
Where did the streaming go(just like claude.ai and every other LLM interaction is like?)????
Where did it go and WHO decided it's a good idea to dump the huge blob of text at the very end?
I'm on Win11 WSL2, 2.1.37 is what keeps me going right now, all the newer versions just keep dumping all response once it's done.
Please bring it back!!
What Should Happen?
The response should present in a progressive way including the thinking process, just like claude.ai
Error Messages/Logs
N/A
Steps to Reproduce
- be on win11
- be on wsl2
- install claude code vscode extension in vscode or cursor
- use it
- experience no-stream response
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.1.37
Claude Code Version
2.1.97
Platform
Other
Operating System
Windows
Terminal/Shell
WSL (Windows Subsystem for Linux)
Additional Information
_No response_
9 Comments
Found 1 possible duplicate issue:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
“Found a duplicate", literally a closed duplicate no one engaged with, bad bot.
hello? anyone seeing this post?
I too am suffering this and Anthropic's aggressive ticket closing using bots is EXTREMELY frustrating for trying to find any information on this. Marking every complaint about this as a duplicate and auto-closing them does nothing for the community and makes it nearly impossible to have a constructive conversation about the issue.
Keep your bots out of the issues threads. They aren't helpful. They're like overzealous, BAD community moderators.
Maybe prioritize fixing issues over closing issues?
Instead you just auto-close all issues that don't get a response within 7 days.
If you're going to ruin your application with untested AI slop, at least let us have a bot free conversation about how your slop is impacting us.
There's no way in hell any human being tested your changes and thought to themselves "this is an improvement".
Streaming tokens so that the human can start reading sooner is like AI Applications 101!
Tested on my machine and this solution resolve it.
20260510 Edited: Adjusted the fix so it works across different JS minifier results for different extension version.
---
The (DIY) Fix
Finally, reload the VS Code window (
Ctrl+Shift+P→Developer: Reload Window) and start a new conversation in Claude Code. Newly spawned Claude processes will now include--include-partial-messagesin their args.To revert:
---
Why this happens
The extension's
spawnClaudemethod setsincludePartialMessages:!<var>.env.remoteName(the minified variable name varies per build, e.g.G4,O0). In WSL2,.env.remoteNameevaluates to"wsl"(truthy), so the expression becomesfalse, and--include-partial-messagesis never passed to the Claude CLI process. Without that flag, the CLI only emits complete assistant content blocks — no incrementalcontent_block_deltaevents reach the webview, so all text appears at once.The data path in normal operation is: Claude CLI stdout (
stream-json) → extension host pipe →QKline-delimited JSON decoder →kOasync iterator →for awaitloop inlaunchClaude→webview.postMessage({type:"from-extension"})→ webviewreadMessages→processStreamEventhandlescontent_block_deltaevents for incremental rendering. The single flag--include-partial-messagescontrols whether the first step produces deltas or only complete blocks.All versions from 2.1.131 through 2.1.138 are affected. The fix is safe: the extension already uses the same
stream-jsonformat andpostMessagetransport regardless of environment — the flag only gates emission granularity at the CLI level, not the transport mechanism.---
Credits and Notes
DeepSeek V4 Proin theClaude Code environment..vscode-server/extensions/, traced thespawnClaude→spawnLocalProcess→ CLI flag assembly chain via grep/context extraction, and cross-checked with live process args fromps.@Deleeete very thank,this is good
Still an issue, not stale.
when to fix it? vscode remote ssh environment, claude code plugin no stream output!!! so terrible experience
Still an issue, not stale.