AI Coding Weekly

Vercel claims up to 25x lower latency in Workflow SDK 5

Guillermo Rauch says time to first step and time between steps both improved, and the durability log is now a standalone package.

Vercel says Workflow SDK 5 cuts latency and overhead up to 25x, encrypts every payload by default, and adds regional workload isolation and failover. The pitch in the announcement is narrow and specific. It is "built for fast agent loops", not for generic background jobs.

Vercel
@vercel
X
Workflow SDK 5 is built for fast agent loops.
Nov 13, 2026 路 View on X

Guillermo Rauch filled in where the time went. He says the "time to first step" and "time between steps" have massively improved, that Vercel doubled down on encryption and security, and that the reliability of the overall system has been proven at massive scale after ironing out subtle details and exercising disaster-recovery scenarios. He did not publish numbers for either timing.

The piece most likely to matter outside Vercel is the last item on his list. The durability log that sits under Workflows has been pulled out as a reusable package called durable-harness, which Rauch says is usable by any agent harness. That is the component that records what a long-running agent has already done so a crashed or resumed run picks up where it left off instead of replaying work.

What the number does and does not cover

Up to 25x is a ceiling on latency and overhead in the orchestration layer, the glue that decides when the next step runs and hands state between steps. It is not a model claim and nothing in either post says anything about tokens or model throughput. If your agent is one long call to a frontier model, the glue was never your bottleneck and this changes nothing you can feel. If your loop is dozens of short durable steps, each one paying the scheduling and state cost, that is exactly where the saving is supposed to land.

Also worth reading precisely. "Up to" is a best case, and Vercel has not shown the workload that produces it, so there is no way yet to tell whether a typical tool-calling loop sees 25x, 2x, or something in between. Neither post includes a benchmark, a before and after chart, or a reference workload.

The encryption change is the one that needs no caveat. Every payload encrypted by default means step inputs and outputs, which in an agent loop are often raw model output, file contents and credentials in flight, are no longer stored in the clear by default. Regional workload isolation and failover is a deployment-level change rather than a developer-facing API change, so it should show up as uptime rather than as code you write differently.

Vercel has been shipping agent infrastructure publicly for a while now, including the security review agent that earlier found 57,897 vulnerabilities and patched 14,665 in a week. Workflow SDK 5 is the plumbing under that kind of thing.

Guillermo Rauch
@rauchg
X
We made the underlying durability log reusable for any agent harness. 饾殟饾殲饾殯饾殜饾殝饾殨饾殠-饾殤饾殜饾殯饾殫饾殠饾殰饾殰 was born.
Nov 13, 2026 路 View on X

Have the good opinion, not the loud one

One email a day. Under three minutes. What working engineers found out about coding with AI.

Get the next one by email

Coding with AI, read daily so you do not have to. The experiments, the receipts and the arguments from engineers shipping real software. Not a changelog.