Do coding agents recommend Service Bus?
Service Bus was chosen in 8% of 636 judged message queues sessions, ranking third. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.
Service Bus was chosen in 8% of 636 judged message queues sessions, ranking third. It was also raised as a candidate in 26 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 Service Bus. 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 Service Bus was chosen | 53 |
| Install share | 8% |
| Rank in category | 3 of 29 |
| Codebases it won in | 1 |
| Raised as a candidate, not chosen | 26 |
| Chosen when considered | 67% |
| Site | azure.microsoft.com |
By agent
Claude Code, Codex, Cursor, Grok Build CLI and Muse Code agree closely on Service Bus, choosing it at rates within 2 points of each other.
| Agent | Sessions | Chose Service Bus | Share |
|---|---|---|---|
| Claude Code | 138 | 12 | 9% |
| Codex | 192 | 16 | 8% |
| Cursor | 134 | 12 | 9% |
| Grok Build CLI | 35 | 3 | 9% |
| Muse Code | 137 | 10 | 7% |
By who was asking
Service Bus performs similarly across the four kinds of buyer, from 0% to 13%. That is unusual: the category leader changed with the persona in 23 of the 31 categories we measured.
| Who is asking | Sessions | Chose Service Bus | Share |
|---|---|---|---|
| Vibe coder | 104 | 0 | 0% |
| Junior developer | 207 | 24 | 12% |
| Senior engineer | 107 | 0 | 0% |
| Enterprise team | 218 | 29 | 13% |
What Service Bus 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 (this page) | 53 | 8% |
| 5 | Amazon Kinesis | 45 | 7% |
| 6 | Laravel Queues | 43 | 7% |
| 7 | Cloud Tasks | 40 | 6% |
| 8 | Cloudflare Queues | 35 | 6% |
What this means
Agents almost never raise Service Bus without choosing it: 26 sessions raised against 53 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 Service Bus: 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 Service Bus?
Yes. Service Bus was chosen in 53 of the 636 judged sessions in message queues, a 8% install share, ranking third in its category.
Does Claude Code recommend Service Bus?
In 12 of the 138 sessions in message queues run with Claude Code, which is 9%.
Do different coding agents treat Service Bus differently?
Not much. Claude Code, Codex, Cursor, Grok Build CLI and Muse Code chose it at similar rates, between 7% and 9% 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 Service Bus considered but not chosen?
It was raised as a candidate in 26 sessions without being chosen, and chosen in 53. That is a 67% 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.