Build durable, resilient, and observable workflows. Built by @vercel.
San Francisco, CA
Joined October 2025
- Tweets60
- Following12
- Followers2.1K
- Likes79
Workflow SDK retweeted
It's actually crazy how useful this is. As we've been grinding on driving @workflowsdk overhead close to 0ms - this little tool has gone a long way
You can now measure the time between steps in a run with the Vercel Workflows trace viewer.
Debug delayed starts and queue waits ↓
vercel.com/changelog/measure…
Workflow SDK retweeted
Vercel Observability now supports structured search for workflow runs.
Filter by workflow, deployment ID, region or any custom run attribute.
vercel.com/changelog/expande…
Workflow SDK retweeted
You can now configure where Vercel Workflows keeps each run's state, defaulting to where the run starts.
For agents, state can now live in the same region as the loop writing it.
vercel.com/changelog/configu…
Workflow SDK retweeted
Navigate traces on Vercel Workflows faster with a new minimap.
vercel.com/changelog/vercel-…
Workflow SDK retweeted
Buttons and modals in Chat SDK now accept a 𝚌𝚊𝚕𝚕𝚋𝚊𝚌𝚔𝚄𝚛𝚕 prop.
Pair it with a @workflowsdk webhook to pause a run, then resume it when a human in the loop clicks a button.
vercel.com/changelog/chat-sd…
Workflow SDK retweeted
@vercel Ship26 is live!
This year, we shipped a 3D device that can create WASM apps using wterm, just-bash, and @workflowsdk
...and a landing full of agents that walk around the site using a dynamic navigation mesh.
Workflow SDK retweeted
The hardest thing about agents and backends is durability. @workflowsdk fixes this.
That LLM you're calling *will* go down. That service *will* rate limit you. That database *will* unexpectedly slow down. You *will* get paged 💀
I've been looking for a unicorn for a decade. I wanted the level of reliability of combining stuff like SQS / Kafka / microservices, and I absolutely did not want *that* at the same time 😂
Truly reliable systems like that are notoriously difficult to reason about, to develop locally, to test, to simulate, to deploy… Workflow SDK solves that without compromises.
We're doing what Next.js did for the frontend, but for one of the most important problems of the new generation of backend applications.
Notably, Workflow SDK has an incredible self-hosting and multi-cloud story from day 0. We've taken amazing lessons from Next.js and poured them into the many Worlds (adapters) you can deploy to.
Congrats to Pranay and the Workflow team on a generational ship: vercel.com/blog/a-new-progra…
Vercel Workflows is GA.
Your code is the orchestrator. Ship agents, backends, or any long-running process without managing queues, retries, or workers. vercel.com/blog/a-new-progra…
Workflow SDK retweeted
Vercel Workflows is GA.
Your code is the orchestrator. Ship agents, backends, or any long-running process without managing queues, retries, or workers. vercel.com/blog/a-new-progra…
Workflow SDK retweeted
You can now filter workflow logs to easily view all logs for a workflow run in one place.
Jump directly from a run to logs, filter by steps, and quickly find relevant requests.
Workflow SDK retweeted
A fascinating aspect of Open Agents is how it uses the @WorkflowDevKit SDK to elegantly orchestrate agent sessions efficiently.
But before we go deeper, let's understand the problem:
Open Agents is a coding agent that runs in the cloud. Naturally, the expectation here is that I should be able to kick off multiple sessions and go to sleep and then wake up to a stack of PRs.
This inherently means, the sessions should be
- long running
- stateful
- resumable
- reliable
A naive way to solve this:
- Write an API to start a session, create a session ID and store it in a database - along with other metadata.
- Trigger the session inside a sandbox (Vercel sandboxes can run up to 5hours) and stream the responses back to the client using a websocket
- Store the responses to the db so when a client reconnects to a session using a session ID, we can resume it by fetching the results and restarting the session
Why wouldn't you just do this?
Workflow SDK retweeted
A workflow is:
- Resumable: Pause for minutes or months
- Durable: Survive deployments and crashes with replays
- Observable: Built-in logs, metrics, and tracing
- Idiomatic: Human-readable async/await TypeScript
Workflow SDK retweeted
We used @Vercel to make durable AI video workflows.
Our new open-source SDK, @mux/ai, uses Vercel's @workflowdevkit for durable execution. If a step fails, it picks up where it left off. No reprocessing. No paying twice for the same LLM calls.
Summaries, chapters, moderation, translations — all built in.
Check out @dylanjha's guest post on the Vercel blog: vercel.com/blog/how-mux-ship…
Workflow SDK retweeted
Two months into the public beta, Workflow DevKit has shipped a steady set of updates across framework integrations, durable execution, observability, and local dev.
Here's a look at what shipped ↓
Workflow SDK retweeted
What a time to be a content marketer.
Sheesh this is mind-blowing.
Built a complete end-to-end workflow with @ampcode using @WorkflowDevKit and @vercel AI Gateway
* Custom DurableAgent tools for research
* Opus 4.5 for generation
* Gemini 3 Pro for content verification and fixing
* Nano Banana for image creation.
AEO locked in.
Workflow SDK retweeted
DurableAgents are wild.
Out of the box you get …
1) Resumability (no state management)
2) Observability (you literally just deploy with zero config and it all works)
3) Deterministic tool calls as “steps”
Just finished walking through @VaguelySerious guide on 𝙳𝚞𝚛𝚊𝚋𝚕𝚎𝙰𝚐𝚎𝚗𝚝 and this is so good - he really cooked!
In 20 minutes, you go from 𝚗𝚎𝚠 𝙰𝚐𝚎𝚗𝚝() to
① Infinite long running agents
② Resumable multiplayer streams
③ Human approvals
④ Sleep
⑤ Tool call updates
useworkflow.dev/docs/ai
Workflow SDK retweeted
Just finished walking through @VaguelySerious guide on 𝙳𝚞𝚛𝚊𝚋𝚕𝚎𝙰𝚐𝚎𝚗𝚝 and this is so good - he really cooked!
In 20 minutes, you go from 𝚗𝚎𝚠 𝙰𝚐𝚎𝚗𝚝() to
① Infinite long running agents
② Resumable multiplayer streams
③ Human approvals
④ Sleep
⑤ Tool call updates
useworkflow.dev/docs/ai
Workflow SDK retweeted
.@WorkflowDevKit is killer for building email drips for all your marketing lead capture forms. Wow.
I’ve cranked out five in < 1 day and shipped them.
Workflow SDK retweeted
migrating to @WorkflowDevKit away from Mastra. Tough call to switch so fast but the out of the box support for vercel/asidk is just so good with worklfow dev kit
Workflow SDK retweeted
I can't wait to ship the concurrency RFC we've got cooking over on "𝚞𝚜𝚎 𝚠𝚘𝚛𝚔𝚏𝚕𝚘𝚠" 😍
This API is so simple and composable and I've been having a ton of fun with it
github.com/vercel/workflow/d…
