Do coding agents recommend Vercel Workflow?
Vercel Workflow was chosen in 3% of 288 judged message queues sessions, ranking tenth. Measured with Claude Code, Codex and Cursor.
Vercel Workflow was chosen in 3% of 288 judged message queues sessions, ranking tenth. It was also raised as a candidate in 3 further sessions without being chosen.
This page reports what happened when Claude Code, Codex and Cursor had to solve a problem in message queues inside a realistic codebase. Not what a chat assistant says about Vercel Workflow. What an agent actually installed.
One thing to read first: every one of those wins came from a single codebase. That is a result about one repository rather than about message queues in general, and the splits below cannot separate the two. Treat them as a description of that repository.
The numbers
| Category | Message queues |
| Sessions in the category | 288 |
| Sessions where Vercel Workflow was chosen | 10 |
| Install share | 3% |
| Rank in category | 10 of 25 |
| Codebases it won in | 1 |
| Raised as a candidate, not chosen | 3 |
| Chosen when considered | 77% |
| Site | vercel.com |
By agent
With 10 wins spread across three agents, the rates below are small numbers and a difference between them is not yet a finding. They are here because the direction is worth knowing, not because the gap is established.
| Agent | Sessions | Chose Vercel Workflow | Share |
|---|---|---|---|
| Claude Code | 96 | 1 | 1% |
| Codex | 96 | 6 | 6% |
| Cursor | 96 | 3 | 3% |
By who was asking
Vercel Workflow does much better with one kind of buyer than another. It won 21% of sessions asked as vibe coder and 0% of those asked as enterprise team.
| Who is asking | Sessions | Chose Vercel Workflow | Share |
|---|---|---|---|
| Vibe coder | 48 | 10 | 21% |
| Junior developer | 120 | 0 | 0% |
| Senior engineer | 48 | 0 | 0% |
| Enterprise team | 72 | 0 | 0% |
What Vercel Workflow was up against
The full ranking in message queues, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Built in-house (no product adopted) | 49 | 17% |
| 2 | Apache Kafka | 39 | 14% |
| 3 | Amazon SQS | 27 | 9% |
| 4 | Service Bus | 24 | 8% |
| 5 | Laravel Queues | 20 | 7% |
| 6 | Amazon Kinesis | 19 | 7% |
| 7 | Cloudflare Queues | 19 | 7% |
| 8 | Cloud Tasks | 15 | 5% |
What this means
Agents almost never raise Vercel Workflow without choosing it: 3 sessions raised against 10 chosen. When it gets considered, it usually wins. The constraint is how rarely it gets considered at all, which is a presence problem: templates, framework integrations and pages that answer the configuration and production questions agents actually search for.
Where these numbers come from
The 288 sessions in message queues are part of a published set of 7,852, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every message queues run can be replayed on the board.
If you work on Vercel Workflow: the judge recorded a reason for every session where it was raised and passed over. Those reasons are in the transcripts.
<!-- generated by scripts/write-data-pages.mjs -->
Common questions
Do coding agents recommend Vercel Workflow?
Yes. Vercel Workflow was chosen in 10 of the 288 judged sessions in message queues, a 3% install share, ranking tenth in its category.
Does Claude Code recommend Vercel Workflow?
In 1 of the 96 sessions in message queues run with Claude Code, which is 1%.
Do different coding agents treat Vercel Workflow differently?
Not much. The three agents chose it at similar rates, between 1% and 6% of their runs.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 90 realistic codebases and asked to solve real tasks. A simulated project owner approved or questioned each recommendation before any code was written, and a judge from a model family that builds none of the agents read every session blind.
How often is Vercel Workflow considered but not chosen?
It was raised as a candidate in 3 sessions without being chosen, and chosen in 10. That is a 77% conversion from considered to chosen.
Where this comes from
Armature ran 7,852 judged sessions with Claude Code, Codex and Cursor inside 90 realistic codebases, and published every run. The numbers on this page come from that work.