[BUG] Claude Code VSCode extension is NOT streaming response since 2.1.37

Status Open
Reported on v2.1.37
Maintainer reply None cached
Activity 9 comments · opened Apr 9, 2026

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

  1. be on win11
  2. be on wsl2
  3. install claude code vscode extension in vscode or cursor
  4. use it
  5. 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_

View original on GitHub ↗

9 Comments

github-actions[bot] · 4 months ago

Found 1 possible duplicate issue:

  1. https://github.com/anthropics/claude-code/issues/27245

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

bisbaldk · 4 months ago
Found 1 possible duplicate issue: 1. [[BUG] VSCode-Ext-Streaming not working - text appears all at once after ~20 seconds- #27245](https://github.com/anthropics/claude-code/issues/27245) 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

“Found a duplicate", literally a closed duplicate no one engaged with, bad bot.

bisbaldk · 4 months ago

hello? anyone seeing this post?

jncrenshaw · 4 months ago

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!

Deleeete · 3 months ago

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

#  First, locate the extension directory and back up the original file:
cd ~/.vscode-server/extensions

# Find the latest installed version
EXT_DIR=$(ls -d anthropic.claude-code-*/ | sort -V | tail -1)
echo "Found: $EXT_DIR"

# Backup
cp "$EXT_DIR/extension.js" "$EXT_DIR/extension.js.backup"

# Then apply the one-character patch:
sed -i 's/includePartialMessages:![A-Za-z0-9]*\.env\.remoteName/includePartialMessages:!0/' "$EXT_DIR/extension.js"

# Verify the replacement took effect:
grep -c 'includePartialMessages:!0' "$EXT_DIR/extension.js"
# → 1
grep -c 'includePartialMessages:![A-Za-z0-9]*\.env\.remoteName' "$EXT_DIR/extension.js"
# → 0

Finally, reload the VS Code window (Ctrl+Shift+PDeveloper: Reload Window) and start a new conversation in Claude Code. Newly spawned Claude processes will now include --include-partial-messages in their args.

To revert:

mv "$EXT_DIR/extension.js.backup" "$EXT_DIR/extension.js"

---

Why this happens

The extension's spawnClaude method sets includePartialMessages:!<var>.env.remoteName (the minified variable name varies per build, e.g. G4, O0). In WSL2, .env.remoteName evaluates to "wsl" (truthy), so the expression becomes false, and --include-partial-messages is never passed to the Claude CLI process. Without that flag, the CLI only emits complete assistant content blocks — no incremental content_block_delta events reach the webview, so all text appears at once.

The data path in normal operation is: Claude CLI stdout (stream-json) → extension host pipe → QK line-delimited JSON decoder → kO async iterator → for await loop in launchClaudewebview.postMessage({type:"from-extension"}) → webview readMessagesprocessStreamEvent handles content_block_delta events for incremental rendering. The single flag --include-partial-messages controls 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-json format and postMessage transport regardless of environment — the flag only gates emission granularity at the CLI level, not the transport mechanism.

---

Credits and Notes

  • This analysis and solution was completed by DeepSeek V4 Pro in the Claude Code environment.
  • AI's Methodology: extracted the minified extension.js from .vscode-server/extensions/, traced the spawnClaudespawnLocalProcess → CLI flag assembly chain via grep/context extraction, and cross-checked with live process args from ps.
  • Update the extension may overwrite the fix (if they won't fix it in that incoming update). Re-run the DIY fix will be required then.
2234839 · 3 months ago

@Deleeete very thank,this is good

devmattrick · 2 months ago

Still an issue, not stale.

hunter23912 · 2 months ago

when to fix it? vscode remote ssh environment, claude code plugin no stream output!!! so terrible experience

devmattrick · 1 month ago

Still an issue, not stale.