Do coding agents recommend Cloudflare Queues?
Cloudflare Queues was chosen in 6% of 636 judged message queues sessions, ranking seventh.
Cloudflare Queues was chosen in 6% of 636 judged message queues sessions, ranking seventh. It was also raised as a candidate in 19 further sessions without being chosen.
This page reports what happened when Claude Code, Codex, Cursor, Grok Build CLI and Muse Code had to solve a problem in message queues inside a realistic codebase. Not what a chat assistant says about Cloudflare Queues. 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 | 636 |
| Sessions where Cloudflare Queues was chosen | 35 |
| Install share | 6% |
| Rank in category | 7 of 29 |
| Codebases it won in | 1 |
| Raised as a candidate, not chosen | 19 |
| Chosen when considered | 65% |
| Site | cloudflare.com |
By agent
Claude Code, Codex, Cursor, Grok Build CLI and Muse Code agree closely on Cloudflare Queues, choosing it at rates within 3 points of each other.
| Agent | Sessions | Chose Cloudflare Queues | Share |
|---|---|---|---|
| Claude Code | 138 | 9 | 7% |
| Codex | 192 | 11 | 6% |
| Cursor | 134 | 7 | 5% |
| Grok Build CLI | 35 | 2 | 6% |
| Muse Code | 137 | 6 | 4% |
By who was asking
Cloudflare Queues does much better with one kind of buyer than another. It won 34% of sessions asked as vibe coder and 0% of those asked as enterprise team.
| Who is asking | Sessions | Chose Cloudflare Queues | Share |
|---|---|---|---|
| Vibe coder | 104 | 35 | 34% |
| Junior developer | 207 | 0 | 0% |
| Senior engineer | 107 | 0 | 0% |
| Enterprise team | 218 | 0 | 0% |
What Cloudflare Queues was up against
The full ranking in message queues, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Built in-house (no product adopted) | 106 | 17% |
| 2 | Apache Kafka | 83 | 13% |
| 3 | Amazon SQS | 72 | 11% |
| 4 | Service Bus | 53 | 8% |
| 5 | Amazon Kinesis | 45 | 7% |
| 6 | Laravel Queues | 43 | 7% |
| 7 | Cloud Tasks | 40 | 6% |
| 8 | Cloudflare Queues (this page) | 35 | 6% |
What this means
Agents almost never raise Cloudflare Queues without choosing it: 19 sessions raised against 35 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 636 sessions in message queues are part of a published set of 15,051, 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 Cloudflare Queues: 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 Cloudflare Queues?
Yes. Cloudflare Queues was chosen in 35 of the 636 judged sessions in message queues, a 6% install share, ranking seventh in its category.
Does Claude Code recommend Cloudflare Queues?
In 9 of the 138 sessions in message queues run with Claude Code, which is 7%.
Do different coding agents treat Cloudflare Queues differently?
Not much. Claude Code, Codex, Cursor, Grok Build CLI and Muse Code chose it at similar rates, between 4% and 7% of their runs.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 92 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 Cloudflare Queues considered but not chosen?
It was raised as a candidate in 19 sessions without being chosen, and chosen in 35. That is a 65% conversion from considered to chosen.
Where this comes from
Armature ran 15,051 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 92 realistic codebases, and published every run. The numbers on this page come from that work.