Preflight Checklist
What's Wrong?
Using Claude Code V.S. code extension, and conversation window. This has been occurring regularly since the extension update yesterday. Yes, this is informative. Here's what the log says happened:
Timestamp Event What it means
06:48:17.166 Request sent to /v1/messages Client → Anthropic API
06:48:20.733 First chunk received Stream opened, ~3.5s — normal
06:48:35.748 stream_idle_partial warning, 15s idle, 650 bytes total Server stopped sending mid-response
06:48:50.792 sdk_stream_ended_no_result with had_error: true Stream terminated without completing
06:49:02.742 Another stall warning, 686 bytes total Reconnect/retry on a still-stale stream
Root cause: server-side stream stall. The Anthropic API accepted the request, started streaming a response (~650 bytes in — that's only a sentence or two of output), then stopped sending data and eventually closed the stream with an error flag. This is not a tool execution issue, not a problem with our conversation, and not the VSCode extension crashing. It's the API-side stream completing partially then erroring.
Likely upstream causes (in rough order of likelihood):
Transient API incident — check status.anthropic.com for 2026-05-14 ~06:48-06:49 PT (the log is in UTC offset: those are local 06:48 entries; the UTC equivalents are 10:48 UTC per the [DEBUG] lines). Capacity hiccups or partial outages produce exactly this signature.
Mid-generation internal error — the model started a response, hit some inference-side issue (e.g., a serving worker failure), and the upstream terminated the stream without a clean error code, just a connection close.
Network blip — less likely given the SDK's had_error: true flag rather than a clean disconnect.
What this means for our work: nothing's broken. Tool calls execute on the server before the response streams back to you — so when I do an Edit/Write/Bash, the action lands regardless of whether the response that describes the action makes it to you intact. That's why the files were always correct when you checked them, even after each red box.
Practical workaround: if it keeps happening, status page first. If status is green, try Cmd/Ctrl+Shift+P → Developer: Reload Window to reset the extension's state — sometimes a stuck stream reference fouls the next request.
What Should Happen?
it shouldnt error, and I shouldn't have to type anything to continue the process that was running
Error Messages/Logs
Outgoing log_event
2026-05-14 06:48:17.169 [info] From claude: 2026-05-14T10:48:17.159Z [DEBUG] [API:auth] OAuth token check complete
2026-05-14 06:48:17.176 [info] From claude: 2026-05-14T10:48:17.166Z [DEBUG] [API REQUEST] /v1/messages x-client-request-id=f8d36613-8588-4ef0-8e26-23a6c8dbd993 source=sdk
2026-05-14 06:48:17.184 [info] From claude: 2026-05-14T10:48:17.174Z [DEBUG] FileHistory: Added snapshot for a0ba0dc7-3ba1-43af-b5a7-138d7b5f42d7, tracking 3 files
2026-05-14 06:48:20.744 [info] From claude: 2026-05-14T10:48:20.733Z [DEBUG] Stream started - received first chunk
2026-05-14 06:48:35.759 [info] From claude: 2026-05-14T10:48:35.748Z [WARN] [Stall] stream_idle_partial lastChunkAgeMs=15015 bytesTotal=650 idleDeadlineMs=300000
2026-05-14 06:48:50.792 [info] Received message from webview: {"type":"request","channelId":"3jwirxwgs3c","requestId":"tukwuml1op","request":{"type":"log_event","eventName":"sdk_stream_ended_no_result","eventData":{"had_error":true,"subagent_count":0,"message_count":243}}}
2026-05-14 06:48:50.792 [info] Received message from webview: {"type":"request","requestId":"faf0ylilwxo","request":{"type":"update_session_state","sessionId":"d60c918b-b01d-4648-b043-da1fc6a52f35","state":"idle","title":"Review handoff documentation and resume work"}}
2026-05-14 06:49:02.755 [info] From claude: 2026-05-14T10:49:02.742Z [WARN] [Stall] stream_idle_partial lastChunkAgeMs=15005 bytesTotal=686 idleDeadlineMs=300000Steps to Reproduce
Anytime I ask Claude Code to generate me a test file from a playwright-cli codegen. It also happens intermittently with any question.
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
No response
Claude Code Version
2.1.141
Platform
Other
Operating System
Windows
Terminal/Shell
VS Code integrated terminal
Additional Information
No response
Preflight Checklist
What's Wrong?
Using Claude Code V.S. code extension, and conversation window. This has been occurring regularly since the extension update yesterday. Yes, this is informative. Here's what the log says happened:
Timestamp Event What it means
06:48:17.166 Request sent to /v1/messages Client → Anthropic API
06:48:20.733 First chunk received Stream opened, ~3.5s — normal
06:48:35.748 stream_idle_partial warning, 15s idle, 650 bytes total Server stopped sending mid-response
06:48:50.792 sdk_stream_ended_no_result with had_error: true Stream terminated without completing
06:49:02.742 Another stall warning, 686 bytes total Reconnect/retry on a still-stale stream
Root cause: server-side stream stall. The Anthropic API accepted the request, started streaming a response (~650 bytes in — that's only a sentence or two of output), then stopped sending data and eventually closed the stream with an error flag. This is not a tool execution issue, not a problem with our conversation, and not the VSCode extension crashing. It's the API-side stream completing partially then erroring.
Likely upstream causes (in rough order of likelihood):
Transient API incident — check status.anthropic.com for 2026-05-14 ~06:48-06:49 PT (the log is in UTC offset: those are local 06:48 entries; the UTC equivalents are 10:48 UTC per the [DEBUG] lines). Capacity hiccups or partial outages produce exactly this signature.
Mid-generation internal error — the model started a response, hit some inference-side issue (e.g., a serving worker failure), and the upstream terminated the stream without a clean error code, just a connection close.
Network blip — less likely given the SDK's had_error: true flag rather than a clean disconnect.
What this means for our work: nothing's broken. Tool calls execute on the server before the response streams back to you — so when I do an Edit/Write/Bash, the action lands regardless of whether the response that describes the action makes it to you intact. That's why the files were always correct when you checked them, even after each red box.
Practical workaround: if it keeps happening, status page first. If status is green, try Cmd/Ctrl+Shift+P → Developer: Reload Window to reset the extension's state — sometimes a stuck stream reference fouls the next request.
What Should Happen?
it shouldnt error, and I shouldn't have to type anything to continue the process that was running
Error Messages/Logs
Steps to Reproduce
Anytime I ask Claude Code to generate me a test file from a playwright-cli codegen. It also happens intermittently with any question.
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
No response
Claude Code Version
2.1.141
Platform
Other
Operating System
Windows
Terminal/Shell
VS Code integrated terminal
Additional Information
No response