Bug: SSE /event stream closes immediately after server.connected event

[lokikl]

Description

Description:

The opencode server's event stream (GET /event) terminates the connection immediately after sending the initial server.connected event. No subsequent bus events (e.g., message.part.delta, message.part.updated) are received by the client, despite the server logs showing that these events are being published internally.

Environment:

• OS: Linux Ubuntu 24.04
• OpenCode version: 1.14.46 (Broken) / 1.14.41 (Working)
• Install method: curl -fsSL https://opencode.ai/install | bash

Steps to reproduce:

1. Run opencode serve.
2. Connect to the event stream using curl -sN http://localhost:4096/event.
3. In another terminal, send a prompt to a session via the HTTP API (e.g., using POST /session/:id/message). (or simply opencode attach http://localhost:4096 and send something)
4. Observe that the curl connection closes immediately after the server.connected event, and no message events are streamed.

Verification:

• Server Logs: opencode.log confirms that events are being published to the internal bus (e.g., service=bus type=message.part.delta publishing).
• Direct API Test: curl -vN http://localhost:4096/event returns HTTP 200 OK and the first event, but then the connection is closed by the server.
• Version Regression: The issue is present in v1.14.46 but is completely resolved when rolling back to v1.14.41.

Likely cause:

The regression appears to have been introduced between v1.14.41 and v1.14.46. A strong suspect is the introduction of HTTP API response compression in v1.14.42, which may be incorrectly buffering or terminating the long-lived SSE stream.

OpenCode version

1.14.46

Operating System

Ubuntu 24.04

Terminal

WezTerm

[github-actions]

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

• prompt_async silently discards requests in v1.14.44 (SSE path broken) #26635: Same symptom — SSE /event stream only receives server.connected and then closes with no subsequent events (message.part.delta, etc.) after using prompt_async. That issue also identifies this as a regression starting in v1.14.44+, which overlaps with your reported broken version (v1.14.46).

[lokikl]

I found that v1.14.41 works, but v1.14.42 is already broken. This narrows the regression window down to the changes introduced in v1.14.42.

[sudo-tee]

This affect my opencode plugin, It does not work anymore when streaming new messages.

sudo-tee/opencode.nvim#374

[KryptXBSA]

I’m experiencing the same issue. v1.14.41 works, but newer versions up to 1.14.48 are broken.

[dtinth]

I am experiencing this issue too while testing Kimaki and making my own lightweight Discord bridge. It seems the /event endpoint is no longer used by first-party user interface.

Instead, both the TUI and the Web app now uses the /global/event endpoint. Migrating the app to the new SDK method sdk.global.event worked around this issue.

[sudo-tee]

I am experiencing this issue too while testing Kimaki and making my own lightweight Discord bridge. It seems the /event endpoint is no longer used by first-party user interface.

Instead, both the TUI and the Web app now uses the /global/event endpoint. Migrating the app to the new SDK method sdk.global.event worked around this issue.

Thanks for the info. Unfortunately the /global/event does not fix our issue, as the messages do not contain the text property, so we still cannot stream the events to the buffer with it.