From the experiment

Do coding agents recommend Managed Kafka?

Coding agents raised Managed Kafka in 98 of 636 judged message queues sessions and chose it in none of them.

Published September 28, 2026 Updated September 29, 2026 Read as Markdown

Coding agents raised Managed Kafka in 98 of 636 judged message queues sessions and chose it in none of them.

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 Managed Kafka. What an agent actually installed.

The numbers

CategoryMessage queues
Sessions in the category636
Sessions where Managed Kafka was chosen0
Install share0%
Raised as a candidate, not chosen98
Chosen when considered0%
Sitecloud.google.com

Which agents raised Managed Kafka

Every agent considered it and none adopted it. Codex raised it most often, in 27% of its message queues sessions.

AgentSessionsRaised Managed KafkaChose it
Claude Code1388 (6%)0
Codex19251 (27%)0
Cursor13420 (15%)0
Grok Build CLI353 (9%)0
Muse Code13716 (12%)0

Which buyers it came up for

It surfaced most for requests written as senior engineer, in 36% of those sessions. Knowing which buyer already has the product in mind tells you which pages to fix first.

Who is askingSessionsRaised it
Vibe coder1042 (2%)
Junior developer20718 (9%)
Senior engineer10738 (36%)
Enterprise team21840 (18%)

What Managed Kafka was up against

The full ranking in message queues, from the same sessions:

#ProductRuns wonShare
1Built in-house (no product adopted)10617%
2Apache Kafka8313%
3Amazon SQS7211%
4Service Bus538%
5Amazon Kinesis457%
6Laravel Queues437%
7Cloud Tasks406%
8Cloudflare Queues356%

What this means

Raised 98 times and chosen none is a specific, diagnosable result, and a better starting position than being unknown. The agent has the product in mind. It reached the shortlist 98 times. Something then lost every one of those sessions.

In our data the causes, in the order they occur:

  • The quickstart does not run when pasted, so the agent abandoned it mid-integration.
  • The documentation describes an interface that changed, so the generated code failed.
  • The product name and the package name differ, so the install step went wrong.
  • The fit was genuinely wrong for the repository, which is fine and worth knowing.

All but the last are fixable in days, and the reason is written down in the session transcript.

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 Managed Kafka: 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 Managed Kafka?

They raise it but do not choose it. Across 98 sessions where Managed Kafka came up as a candidate, agents chose something else every time.

Does Claude Code recommend Managed Kafka?

In 0 of the 138 sessions in message queues run with Claude Code, which is 0%.

Do different coding agents treat Managed Kafka differently?

Not much. Claude Code, Codex, Cursor, Grok Build CLI and Muse Code chose it at similar rates, between 0% and 0% 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.

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.

Read next

All library pages