Abnormal stop working while coding or analysis

[qamranmushtaq-collab]

Description

when running the codewhale, it suddently showing the error:
Error:
Warn Stream read error: error decoding response body

Steps to reproduce

Expected behavior

Actual behavior

Impact

Environment

• OS:
• codewhale version: windows 11
• codewhale version: 0.8.52
• Install method: npx
• codewhale doctor summary:
• Model/provider: deepseek
• Terminal app: yes
• Shell:

Logs, screenshots, or recordings

[github-actions]

Thanks @qamranmushtaq-collab for the report.

This repository is currently observing a maintainer-managed contribution gate in dry-run mode, so this issue is staying open. When enforcement is enabled, issues from contributors who are not listed in .github/APPROVED_CONTRIBUTORS will be closed automatically.

Please read CONTRIBUTING.md for the expected issue shape. A maintainer can grant issue access by commenting /lgtmi on an issue.

[Hmbown]

Thanks @qamranmushtaq-collab for reporting this. I landed a narrow v0.9 stewardship fix in #2849 (35cd09a9f): CodeWhale now classifies Stream read error: error decoding response body / chunk-body decode failures as recoverable network interruptions instead of generic internal errors, and the taxonomy test covers the exact phrasing from this issue.

Verification on the maintainer PR:

• cargo test -p codewhale-tui error_taxonomy::tests --locked
• git diff --check
• cmp -s CHANGELOG.md crates/tui/CHANGELOG.md
• ./scripts/release/check-versions.sh
• ./scripts/release/check-ohos-deps.sh

I am leaving this issue open because that change improves classification/triage, but it does not prove the underlying Windows 11 + npx + DeepSeek stream interruption is fixed. Could you please add these details when you can, with secrets redacted?

• exact command you ran, including the npx ... invocation
• the output of codewhale --version
• terminal app and shell, for example Windows Terminal + PowerShell or VS Code terminal
• provider/model and whether it happens mostly on long responses
• relevant codewhale doctor lines with API keys redacted
• whether npx codewhale@latest / 0.8.53 still reproduces

That will let us tell whether this is a provider/network interruption, Windows terminal/runtime issue, or an npx packaging edge.