Uh oh!
There was an error while loading. Please reload this page.
fix(opencode): batch direct shell output updates - #37788
Conversation
The following comment was made by an LLM, it may be inaccurate: I found a related PR that appears to be a near-duplicate: Related PR:
Why it's related: |
flowluap
commented
Jul 19, 2026
Related, but they cover separate implementations:
The paths do not call each other and the PRs have no overlapping files. Merging #37653 does not change the per-chunk |
Automated PR Cleanup Thank you for contributing to opencode. Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions. This PR was closed because it matched the following cleanup criteria:
PRs created within the last month are not affected by this cleanup. If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate. Thanks again for taking the time to contribute. |
Issue for this PR
Closes#37787
Type of change
What does this PR do?
The direct user shell awaited a durable part update for every decoded output chunk. This coupled pipe consumption to SQLite projection and event broadcast work.
This change consumes output immediately and publishes the latest cumulative running snapshot at most every 100 ms. A version counter keeps output dirty when bytes arrive during an update. The publisher is interrupted before the existing final part update, so completion remains authoritative and no running update can arrive afterward.
How did you verify your code works?
Screenshots / recordings
N/A
Checklist