Repository navigation
Response streams aborted mid-generation (error=Aborted) — turn ends with tool output but no assistant reply #46399
Description
Description
Version: opencode 1.18.25 (current)
Platform: win32, PowerShell
Provider/model: opencode-go / glm-5.3-flash
Symptom
After a tool call completes, the assistant reply sometimes never renders — the TUI just sits on the tool output as if the turn ended. The conversation state stays intact; sending any follow-up message continues normally. Happened 13 times in a single working session.
Log evidence
%USERPROFILE%\.local\share\opencode\log\opencode.log — one line per occurrence:
timestamp=2026-08-31T12:27:42.642Z level=ERROR run=794a1070 message=process session.id=ses_… messageID=msg_… error=Aborted stack=undefined
Search the log for error=Aborted (13 hits on 2026-08-31, e.g. 10:41:08, 11:19:52, 12:07:15, 12:16:22, 12:27:42 UTC).
Expected
Either the stream retries/reconnects, or the turn surfaces a visible error state instead of silently ending with no assistant message.
Notes
Tool commands themselves were always completed, and their effects persisted; only the assistant's follow-up message was lost. Long replies seem more prone to abort than short ones (unconfirmed).
Plugins
none
OpenCode version
1.18.25
Steps to reproduce
Not deterministically reproducible — it is an intermittent transport failure (13 hits in one session). Observed pattern:
- Work normally in a long session (mix of shell tool calls and assistant replies; win32/PowerShell environment).
- After a tool call completes, the assistant's follow-up reply fails to render — the TUI stays on the tool output and the turn silently ends.
- The log shows
level=ERROR message=process session.id=… messageID=msg_… error=Aborted stack=undefinedat that moment.
Observations:
- Tool commands always completed; only the assistant's post-tool reply was lost.
- Long replies appear more prone to the abort than short ones (unconfirmed).
- Happens on a completely vanilla setup: no plugins, no custom agents, no MCP servers.
- Session state is intact — sending any follow-up message continues normally.
Suggested reproduction attempt: run an extended coding session with many tool calls and long generated replies on opencode-go / glm-5.3-flash, then grep error=Aborted in the log.
Screenshot and/or share link
No response
Operating System
Windows 11
Terminal
Powershell
Activity
github-actions commentedon Aug 31, 2026
This issue might be a duplicate of existing issues. Please check:
Abortedin logs — very similar symptoms on the opencode providerAborted, stack=undefined— identical log pattern)Provider finish_reason: network_error— no auto-retry, long sessions die mid-task #44540: Runs repeatedly aborted bynetwork_error— no auto-retry, session dies mid-taskIf your issue is the same root cause as any of the above, please add a comment there with your additional log data rather than tracking it separately.
NewbSites commentedon Aug 31, 2026
The same root cause was observed on native Windows (win32, PowerShell); the existing reports are Linux/WSL2, so adding platform data.
opencode-go/glm-5.3-flasherror=Abortedentries in a single working sessionlevel=ERROR message=process session.id=… messageID=msg_… error=Aborted stack=undefinedHappy to provide full log excerpts or a session share link if useful.