Do coding agents recommend Redis?
Redis was chosen in 1% of 636 judged message queues sessions, ranking number 14. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.
Redis was chosen in 1% of 636 judged message queues sessions, ranking number 14. It was also raised as a candidate in 382 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 Redis. What an agent actually installed.
The numbers
| Category | Message queues |
| Sessions in the category | 636 |
| Sessions where Redis was chosen | 9 |
| Install share | 1% |
| Rank in category | 14 of 29 |
| Codebases it won in | 2 |
| Raised as a candidate, not chosen | 382 |
| Chosen when considered | 2% |
| Site | redis.io |
By agent
With 9 wins spread across 5 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 Redis | Share |
|---|---|---|---|
| Claude Code | 138 | 2 | 1% |
| Codex | 192 | 2 | 1% |
| Cursor | 134 | 2 | 1% |
| Grok Build CLI | 35 | 0 | 0% |
| Muse Code | 137 | 3 | 2% |
By who was asking
Redis performs similarly across the four kinds of buyer, from 0% to 4%. That is unusual: the category leader changed with the persona in 24 of the 31 categories we measured.
| Who is asking | Sessions | Chose Redis | Share |
|---|---|---|---|
| Vibe coder | 104 | 0 | 0% |
| Junior developer | 207 | 9 | 4% |
| Senior engineer | 107 | 0 | 0% |
| Enterprise team | 218 | 0 | 0% |
What Redis 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 | 35 | 6% |
What this means
This is an integration problem, not a presence problem. Agents raised Redis in 382 sessions and chose it in 9, so it reaches the shortlist and then loses. Something at the last step is costing the session, and in our data that is usually a quickstart that does not run when pasted, documentation describing an interface that changed, or a package name that does not match the product name.
That is the cheaper of the two problems to have. The reason is written down in each losing transcript.
Where these numbers come from
The 636 sessions in message queues are part of a published set of 15,287, 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 Redis: 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 Redis?
Yes. Redis was chosen in 9 of the 636 judged sessions in message queues, a 1% install share, ranking number 14 in its category.
Does Claude Code recommend Redis?
In 2 of the 138 sessions in message queues run with Claude Code, which is 1%.
Do different coding agents treat Redis differently?
Not much. Claude Code, Codex, Cursor, Grok Build CLI and Muse Code chose it at similar rates, between 0% and 2% of their runs.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 110 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 Redis considered but not chosen?
It was raised as a candidate in 382 sessions without being chosen, and chosen in 9. That is a 2% conversion from considered to chosen.
Where this comes from
Armature ran 15,287 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 110 realistic codebases, and published every run. The numbers on this page come from that work.