Workflow SDK reuses WebSockets for event and stream writes
Workflow SDK now sends event and stream writes over WebSockets by default on Vercel, replacing separate HTTP requests for individual writes or stream groups. Existing streaming code can stay unchanged after upgrading to version 5.2.0 or later. New deployments use the new transport for new runs, while in-flight runs finish on their original deployment.
Vercel · Nov 9, 2026
Why it matters
Workflows that emit many steps or token chunks can avoid repeated HTTP request overhead.
More context
The queue handler opens a connection for each delivery. Upgrade and deploy, then test a representative stream for chunk delays. Teams moving from version 4 should read the major-version migration guide rather than treating this as a dependency-only patch.
Keep in mind
Released transport change for Vercel Workflows. Vendor benchmarks use one replayed token stream; they do not establish universal latency gains or new execution guarantees. Platform usage costs still need checking.
Original read