You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a client sends CF_AGENT_STREAM_RESUME_REQUEST and no active stream exists, the agent now responds with CF_AGENT_STREAM_RESUME_NONE instead of waiting for a 5s timeout. Added MessageType.CF_AGENT_STREAM_RESUME_NONE and outgoing message typing, server-side send in index.ts, and client handling in react.tsx to call handleStreamResumeNone. The WebSocket transport gains a _resumeNoneResolver, handleStreamResumeNone(), and wiring in reconnectToStream to resolve immediately with null; timeouts are preserved as a safety net. Tests updated/added to assert the RESUME_NONE message and transport behavior. This eliminates the UI stall on open/switch/refresh when there's no active stream by collapsing the previous 5-second wait to a single WS round-trip.
Server now responds with `CF_AGENT_STREAM_RESUME_NONE` when a client sends `CF_AGENT_STREAM_RESUME_REQUEST` and no active stream exists. This collapses the previous 5-second timeout to a single WebSocket round-trip, fixing the UI stall on every conversation open/switch/refresh when there is no active stream.
0 commit comments