anomalyco / anomalyco/opencode
DeepSeek V4 Flash responses become corrupted with repeated Q characters during long tool-assisted generations
@Brendonovich is already working on this.
Since Aug 3, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Description
While using DeepSeek V4 Flash (Free) through OpenCode, model responses occasionally become corrupted during longer generations.
Instead of producing normal text, portions of the response are replaced with repeated Q characters and malformed words, making the output unreadable.
This appears to happen during or after reasoning/tool execution rather than being a rendering issue in the UI.
Environment
OpenCode: (fill in version/commit)
Model: DeepSeek V4 Flash (Free)
OS: Windows 11
Provider: (OpenRouter/OpenCode provider if applicable)
Steps to Reproduce
- Start a conversation with DeepSeek V4 Flash (Free).
- Give a relatively complex task that requires reasoning and code modifications.
- Wait for the model to generate a long response.
- Occasionally, the generated text becomes corrupted.
Expected Behavior
The model should produce coherent natural language throughout the response.
Example:
Placeholder: use the new 128×128 PNG for both themes...
Actual Behavior
The response becomes filled with repeated Q characters and corrupted words.
Example:
Q-placeholder QSS — low-Q one: embedded Q24×24 base64 PNG QSS app.js:44-45.
Not downloaded → QSS QSSQSSQSS no Q-Q asset.
...
Q migration QSSQ: check files exist...
...
QSS QSS values 44-45...
Later in the same response even PowerShell commands become corrupted:
Test-QPath
QReadQAllQBytes
Qictures
QHost
which makes the generated code unusable.
Frequency
encountered it today for the first time August 4 2026
Models used: deepseek-v4-flash-free
Plugins
No response
OpenCode version
1.18.11
Steps to reproduce
No response
Screenshot and/or share link
Operating System
Windows 11 25H2
Terminal
Windows Terminal (powershel 7)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.