fix(app): pin opencode sidecar+SDK to v1.14.38 to restore live streaming#1772
Open
jonharris0n wants to merge 1 commit into
Open
fix(app): pin opencode sidecar+SDK to v1.14.38 to restore live streaming#1772jonharris0n wants to merge 1 commit into
jonharris0n wants to merge 1 commit into
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
@jonrmls is attempting to deploy a commit to the Different AI Team on Vercel. A member of the Team first needs to authorize it. |
The bump to opencode v1.14.48 (2993b80) regresses live session streaming: after sending a prompt the UI is stuck on the "Thinking" indicator with no user bubble, and the assistant response never appears until the session is refreshed. The session snapshot endpoint still works (which is why refresh recovers), so the regression is in the SSE event path between opencode 1.14.48 and the renderer's session-sync — confirmed empirically by rebuilding the Electron app with the SDK + bundled sidecar pinned back to 1.14.38: chats stream normally again. This is a hot-fix pin to unblock users. A follow-up should bisect 1.14.39..1.14.48 to find the upstream change and adjust session-sync so we can move forward again.
jonharris0n
force-pushed
the
fix/pin-opencode-1.14.38
branch
from
0849e53 to
ef2a8f3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The opencode bump to v1.14.48 in 2993b80 broke live session streaming. After sending a prompt the chat UI is stuck on the "Thinking" indicator — no user bubble appears, and the assistant response never streams in. The conversation only becomes visible after a manual refresh.
The
getSessionSnapshotHTTP endpoint still returns the messages correctly (which is why refresh recovers everything), so the data is reaching opencode fine. The regression sits in the SSE event path between opencode 1.14.48 and the renderer'ssession-sync.ts— somewhere between those versions the live event stream stopped being consumed correctly by our app.I verified empirically: with
applyRevertCursordisabled the bug persists; with the SDK + bundled sidecar pinned back to 1.14.38 (and otherwise unchanged code) chats stream normally again on a fresh Electron build.This PR is a minimal hot-fix: revert
constants.jsonandapps/app/package.jsonto the 1.14.38 line that 2993b80 changed, plus the correspondingpnpm-lock.yamlupdates. No app or server source changes.Repro on the current
devAfter this patch
Same steps; the user bubble appears immediately, assistant reply streams in token-by-token as expected.
Follow-up (not in this PR)
We should bisect opencode 1.14.39…1.14.48 to identify which upstream change broke the SSE shape, then patch
session-sync.applyEvent/normalizeEventso we can bump opencode forward again. The currentapplyEventguards drop events silently when they don't match the expected{type, properties: {info: {id, role, sessionID}}, …}shape — likely candidates are a renamed field, a removedinfo.sessionID, or a new role value outside theuser|assistant|systemwhitelist.Test plan
pnpm installresolves@opencode-ai/sdkto 1.14.38 (verified in lockfile)pnpm --filter @openwork/desktop package:electron:dirsucceeds; bundledversions.jsonshowsopencode: 1.14.38.app, sending a prompt, and watching the response stream in works end-to-end (this was the failing case before the pin)