session.error events are ignored by global sync (stuck busy, no error shown) #48530

Activity

1. github-actions

   assigned

   Brendonovich

   on Sep 11, 2026
2. github-actions commented on Sep 11, 2026

   

   github-actionsBot

   on Sep 11, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • Session run defects are silently dropped — UI shows no error, session just goes idle #42259: Session run defects are silently dropped — UI shows no error, session just goes idle — describes the same root cause: session.error events not being properly surfaced to the UI, leaving the session appearing to succeed or staying in an incorrect state.
   • bug: UI stuck on 'thinking' indefinitely after stream error, no error displayed or state recovery #32366: UI stuck on 'thinking' indefinitely after stream error, no error displayed or state recovery — similar symptom of the session/UI getting stuck with no error shown after a failure.
3. CannonRS commented on Sep 11, 2026

   

   CannonRS

   on Sep 11, 2026

   Author

   More actions

   Not a duplicate of #42259 or #32366; both are related but describe different layers.

   #42259 is a server-side event-ordering problem: \session.error\ is published after \session.status idle, so UI consumers that stop processing on idle never render the error. Its fix (PR #42253) reorders the SSE stream and does not touch the client-side global sync reducer.

   #32366 is a desktop 'stuck on thinking' case after a dropped stream (no state recovery, no retry), a different symptom and environment.

   This issue (#48530) is the client-side counterpart: when a \session.error\ event reaches the store, the global sync reducer (\�pplyDirectoryEvent) ignores it — the session status stays busy, the last assistant message gets no error marker, and no toast is shown. The fix is purely in \�vent-reducer.ts\ / \server-sync.tsx; even with correct server ordering the reducer must first handle the event. The companion PR #48534 touches no file that #42253 touches.
4. neriousy commented on Oct 20, 2026

   

   neriousy

   on Oct 20, 2026

   Member

   More actions

   Thanks for reporting this! Session failures now return the session to idle and display the failure in the desktop conversation, with the error-display fix first released in 2.0.27. Update with opencode upgrade or npm i -g @opencode/cli@latest (desktop: update the app). Please reopen or comment if a failed session still stays busy or hides its error on that version.
5. neriousy

   closed this as completedon Oct 20, 2026