Summary
The Workflow SDK now sends event writes and stream writes to Vercel Workflows over a WebSocket by default. Previously, each write, or each write group for streams, used a separate HTTP request. Developers do not need to change their code, but they must upgrade to [email protected] or later. According to the source, new runs use the WebSocket path once the upgrade is deployed, while in-flight runs finish on the existing behavior.
AI-assisted summary based on the listed source.
What happened
The Workflow SDK now sends event writes and stream writes to Vercel Workflows over a WebSocket by default, replacing one HTTP request per write, or per write group for streams. No code change is needed beyond upgrading to [email protected] or later. Once you deploy the upgrade, new runs use it. In-flight runs finish....
Why it matters
Teams running workflows on Vercel will get the new transport by upgrading the SDK, without rewriting their code. Anyone whose runs are still in progress during a deploy should expect them to finish as before. The source does not give performance figures, so teams should check their own run behavior after upgrading.
Signal Intelligence
Signal Strength 88%
Technical label WATCH
Public Interest 29
Category AI AT WORK
Reader Depth TECHNICAL
Signal Strength reflects source quality, relevance, freshness and evidence. Public Interest helps organize discovery; it is not proof of truth.
Public Interest components
Recognizable Entity Score 0
Practical Impact Score 0
Novelty Interest Score 72
Consequence Score 62
Curiosity Score 16
Shareability Score 41