Claude Code v2.1.141 Regression: Stream Stall and sdk_stream_ended_no_result in Long Sessions

What this error means

Stream stall + sdk_stream_ended_no_result after update to 2.1.141 is a Claude Code failure pattern reported for developers trying to fix claude code streaming stall and no result delivered after v2.1.141 update. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Confirmed regression in v2.1.141. Stream stalls for 15s then had_error: true. Multiple reports across macOS, Windows, Linux. Rolling back to previous version fixes it immediately.

Common causes

• After auto-updating to v2.1.141, long sessions fail with streaming stalls — API completes successfully but no result is delivered to the extension. Rolling back resolves the issue, confirming regression.
• Confirmed regression in v2.1.141. Stream stalls for 15s then had_error: true. Multiple reports across macOS, Windows, Linux. Rolling back to previous version fixes it immediately.

Quick fixes

1. Confirm the exact error signature matches Stream stall + sdk_stream_ended_no_result after update to 2.1.141.
2. Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
3. Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

• Verify the command, editor, extension, or API client that produced the error.
• Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
• Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

1. Capture the exact error message and the command, editor action, or request that triggered it.
2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
3. Review the source evidence below and compare it with your environment.
4. Apply one change at a time and rerun the smallest failing action.
5. Keep the working fix documented for the team or deployment environment.

How to prevent it

• Keep provider/tool configuration documented.
• Record non-secret diagnostics such as tool version, provider name, model name, and command path.
• Add a lightweight check before CI or production workflows depend on the tool.

Sources checked

• https://github.com/anthropics/claude-code/issues/58989
• https://github.com/anthropics/claude-code/issues/59013

Evidence note: Confirmed regression in v2.1.141. Stream stalls for 15s then had_error: true. Multiple reports across macOS, Windows, Linux. Rolling back to previous version fixes it immediately.

Related errors

• Claude Code Unhandled case object Object
• Claude Code desktop app hangs on new messages

FAQ

What should I check first?

Start with the exact Stream stall + sdk_stream_ended_no_result after update to 2.1.141 text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed Claude Code workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without Stream stall + sdk_stream_ended_no_result after update to 2.1.141.