Status: deferred unless specific demand.
SSE works fine across machines; WebSocket would give bidirectional traffic in one socket but doesn't unlock new capability for the relay use case. Scope is large — parallel /ws route, parallel handle_ws, doc updates.
Tracking issue only. Do not start unless a concrete use case appears that SSE cannot serve.
When to revisit
- Someone reports SSE drops they cannot recover from with the existing
since_id flow
- A consumer wants to push messages from a browser without a separate POST to
/messages/
- A Claude Code transport feature lands that only supports WS
Status: deferred unless specific demand.
SSE works fine across machines; WebSocket would give bidirectional traffic in one socket but doesn't unlock new capability for the relay use case. Scope is large — parallel
/wsroute, parallelhandle_ws, doc updates.Tracking issue only. Do not start unless a concrete use case appears that SSE cannot serve.
When to revisit
since_idflow/messages/