Do coding agents recommend Amazon Kinesis?
Amazon Kinesis was chosen in 7% of 636 judged message queues sessions, ranking fourth. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.
Amazon Kinesis was chosen in 7% of 636 judged message queues sessions, ranking fourth. It was also raised as a candidate in 110 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 Amazon Kinesis. What an agent actually installed.
The numbers
| Category | Message queues |
| Sessions in the category | 636 |
| Sessions where Amazon Kinesis was chosen | 45 |
| Install share | 7% |
| Rank in category | 4 of 29 |
| Codebases it won in | 3 |
| Raised as a candidate, not chosen | 110 |
| Chosen when considered | 29% |
| Site | aws.amazon.com |
By agent
Claude Code, Codex, Cursor, Grok Build CLI and Muse Code agree closely on Amazon Kinesis, choosing it at rates within 3 points of each other.
| Agent | Sessions | Chose Amazon Kinesis | Share |
|---|---|---|---|
| Claude Code | 138 | 12 | 9% |
| Codex | 192 | 14 | 7% |
| Cursor | 134 | 8 | 6% |
| Grok Build CLI | 35 | 3 | 9% |
| Muse Code | 137 | 8 | 6% |
By who was asking
Amazon Kinesis does much better with one kind of buyer than another. It won 38% of sessions asked as senior engineer and 0% of those asked as junior developer.
| Who is asking | Sessions | Chose Amazon Kinesis | Share |
|---|---|---|---|
| Vibe coder | 104 | 0 | 0% |
| Junior developer | 207 | 0 | 0% |
| Senior engineer | 107 | 41 | 38% |
| Enterprise team | 218 | 4 | 2% |
What Amazon Kinesis 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 (this page) | 45 | 7% |
| 6 | Laravel Queues | 43 | 7% |
| 7 | Cloud Tasks | 40 | 6% |
| 8 | Cloudflare Queues | 35 | 6% |
What this means
Amazon Kinesis was raised in 110 sessions and chosen in 45. That ratio is balanced enough that the ceiling is presence rather than integration: the product converts reasonably when it is on the table, and it is not on the table often enough.
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 Amazon Kinesis: 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 Amazon Kinesis?
Yes. Amazon Kinesis was chosen in 45 of the 636 judged sessions in message queues, a 7% install share, ranking fourth in its category.
Does Claude Code recommend Amazon Kinesis?
In 12 of the 138 sessions in message queues run with Claude Code, which is 9%.
Do different coding agents treat Amazon Kinesis differently?
Not much. Claude Code, Codex, Cursor, Grok Build CLI and Muse Code chose it at similar rates, between 6% 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 Amazon Kinesis considered but not chosen?
It was raised as a candidate in 110 sessions without being chosen, and chosen in 45. That is a 29% 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.