You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ACP in JetBrains Rider: assistant output chunks are delayed/truncated until next prompt when using GLM5 plugin #15613
When using OpenCode via ACP in JetBrains Rider (confirmed with GLM5 model, possibly other models), assistant output is often not streamed fully in real time. Part of the response appears to be missing/truncated, and the missing content is only flushed/displayed when the next prompt is submitted.
Expected Behavior
Assistant output should stream continuously and completely during a single response, without requiring a follow-up prompt to reveal missing chunks.
Actual Behavior
Initial response appears truncated or incomplete.
Remaining output appears right before (or as part of UI handling for) the next prompt submission.
This creates the perception that streaming stopped early.
This may be related to client handling of incremental events (e.g., message.part.delta vs message.part.updated) or buffering/flush behavior in plugin-side rendering. It appears some chunks are received but not rendered until a subsequent interaction triggers UI flush.
Impact
- Confusing UX (looks like model stopped early).
- Hard to trust completeness of responses.
- Slower workflow due to manual “poke” (next prompt) required to reveal missing text.
Request
Please investigate ACP event/chunk handling in JetBrains plugin integrations and ensure incremental chunks are flushed/rendered immediately, including fallback behavior when only updated events are emitted.
Plugins
OpenCode ACP agent integration in JetBrains Rider
OpenCode version
1.2.15
Steps to reproduce
Start OpenCode ACP agent integration in JetBrains Rider.
Use GLM5 plugin (or another plugin) for a response that streams multiple chunks.
Observe that output appears incomplete at end of generation.
Send a new prompt.
Notice previously missing output appears before the new request is actually sent upstream.
Seriously folks, i appreciate that managing that many contributions is not easy, but this experience is really awful. I've waited for two months without getting any feedback, fixed merge conflicts over that period in my PR as new code got merged, only to see my ticket essentially made irrelevant without getting any feedback.
This is not a way to treat contributors.
Reacted by nilsreich, gluap, matryosha, Denis, HongkaiSong, Chris, Patrick M. Niedzielski and Lukasz Podolak
Activity
github-actions commentedon Mar 1, 2026
This issue might be a duplicate of existing issues. Please check:
nkosi23 commentedon Mar 6, 2026
@thdxr Can you please take a look at my PR? This is a very impacting bug
wudeyong commentedon Mar 12, 2026
Is there a plan to merge this merge request into the main branch?
hancengiz commentedon Mar 14, 2026
I created a seperate issue marked as relevant. fyi. #17505
nkosi23 commentedon May 8, 2026
@thdxr Why have you removed the bug and ACP flag?
Seriously folks, i appreciate that managing that many contributions is not easy, but this experience is really awful. I've waited for two months without getting any feedback, fixed merge conflicts over that period in my PR as new code got merged, only to see my ticket essentially made irrelevant without getting any feedback.
This is not a way to treat contributors.
github-actions commentedon Jul 10, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.