Workflow SDK now writes over WebSockets on Vercel
Workflow SDK 5.2.0 switches event and stream writes to WebSockets by default; Vercel's agent-stream replay delivered a full response 4.2× faster than v4.8.12.
From **workflow@5.2.0**, event and stream writes to Vercel Workflows use WebSockets by default, replacing individual HTTP requests or stream write groups. Existing streaming code needs no changes. In Vercel's replay of an AI agent token stream, **v5.2.0 delivered the full response 4.2× faster than v4.8.12**, with no chunk delayed over a second.
For agent workflows that stream tokens or write many step events, upgrading could reduce request overhead and improve delivery speed. New runs use the deployment's version; in-flight runs finish on the deployment where they started.
From **workflow@5.2.0**, event and stream writes to Vercel Workflows use WebSockets by default, replacing individual HTTP requests or stream write groups. Existing streaming code needs no changes. In Vercel's replay of an AI agent token stream, **v5.2.0 delivered the full response 4.2× faster than v4.8.12**, with no chunk delayed over a second. For agent workflows that stream tokens or write many step events, upgrading could reduce request overhead and improve delivery speed. New runs use the deployment's version; in-flight runs finish on the deployment where they started. Moving from SDK 4.x to 5.x is a major upgrade, so Vercel points users to its upgrade guide. The performance result is from one replay benchmark, not a general latency guarantee.
This Signal changes the transport used for Vercel Workflow event and stream writes: SDK 5.2.0 uses WebSockets by default, with no streaming-code changes. Its 4.2× result is specific to one replay, so it supports evaluating the upgrade for write-heavy workflows but does not establish a general speedup.