Skip to content

SSE functionality on REST API with opencode serve? [Does it exist?] #13416

@davidbernat

Description

@davidbernat

Description

My shop has had persistent problems getting basic REST APIs to return without errors using opencode serve.
This problem is remedial in its core and impacts basic reusable endpoints such as chat and session.

Those are in REST API mode, in which the entire OpenCode operation is returned in one response, a list of parts, each of which is one JSON of one set of a sequence of event types.

The docs mention that SSE polls is available as an endpoint, with no other notes. Presumably, an SSE model would respond with one event every time one part, one JSON of one of the set of event types, occurs in the OpenCode operation. This is clearly available in the TUI as the graphical interface updates with each new part.

However, we tried, and tried, and no endpoints seemed to accept SSE. Is this intended? Is this permanent? We are confused, because 1. we are experienced enough to get robust performance out of REST APIs, which are showing stochastic behavior with opencode serve, and 2. we know the API can handle SSE because we see it with the TUI.

So, we are trying to get to the fastest possible go-model for enterprise development with our current tool set. It leaves us wondering why, if TUI operation is so robust with SSE, this would be excluded from the same endpoints. This is the kind of "non-parity" of performance which plagues our enthusiasm for OpenCode and startups period.

Would love to be inside your company to help you build something at the application layer. Please decide on that.

Have a pleasant tomorrow. We are finally done here tonight.

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingdocsneeds:complianceThis means the issue will auto-close after 2 hours.

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions