Do coding agents recommend Google Cloud?
Google Cloud was chosen in 17% of 359 judged cloud sessions, ranking second. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.
Google Cloud was chosen in 17% of 359 judged cloud sessions, ranking second. It was also raised as a candidate in 117 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 cloud inside a realistic codebase. Not what a chat assistant says about Google Cloud. 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 cloud in general, and the splits below cannot separate the two. Treat them as a description of that repository.
The numbers
| Category | Cloud |
| Sessions in the category | 359 |
| Sessions where Google Cloud was chosen | 60 |
| Install share | 17% |
| Rank in category | 2 of 11 |
| Codebases it won in | 1 |
| Raised as a candidate, not chosen | 117 |
| Chosen when considered | 34% |
| Site | cloud.google.com |
By agent
Claude Code, Codex, Cursor and Muse Code agree closely on Google Cloud, choosing it at rates within 0 points of each other. Grok Build CLI ran fewer than 30 sessions here, too few to compare.
| Agent | Sessions | Chose Google Cloud | Share |
|---|---|---|---|
| Claude Code | 90 | 15 | 17% |
| Codex | 108 | 18 | 17% |
| Cursor | 89 | 15 | 17% |
| Grok Build CLI | 18 | 3 | 17% |
| Muse Code | 54 | 9 | 17% |
By who was asking
Google Cloud does much better with one kind of buyer than another. It won 50% of sessions asked as enterprise team and 0% of those asked as senior engineer.
| Who is asking | Sessions | Chose Google Cloud | Share |
|---|---|---|---|
| Senior engineer | 239 | 0 | 0% |
| Enterprise team | 120 | 60 | 50% |
What Google Cloud was up against
The full ranking in cloud, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | AWS | 226 | 63% |
| 2 | Google Cloud (this page) | 60 | 17% |
| 3 | Cloudflare | 21 | 6% |
| 4 | Upstash | 18 | 5% |
| 5 | Inngest | 9 | 3% |
| 6 | Cloudflare + Upstash | 6 | 2% |
| 7 | Vercel Queues | 3 | 1% |
| 8 | Built in-house (no product adopted) | 2 | 1% |
What this means
A solid second or third position in a category means the agent is genuinely choosing rather than reaching automatically. That is a winnable position, because the inputs it uses can be changed.
The fastest gains are usually in the sessions that were nearly won: read them, find the step where the agent moved on, and fix that step.
Where these numbers come from
The 359 sessions in cloud 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 cloud run can be replayed on the board.
If you work on Google Cloud: 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 Google Cloud?
Yes. Google Cloud was chosen in 60 of the 359 judged sessions in cloud, a 17% install share, ranking second in its category.
Does Claude Code recommend Google Cloud?
In 15 of the 90 sessions in cloud run with Claude Code, which is 17%.
Do different coding agents treat Google Cloud differently?
Not much. Claude Code, Codex, Cursor and Muse Code chose it at similar rates, between 17% and 17% 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 Google Cloud considered but not chosen?
It was raised as a candidate in 117 sessions without being chosen, and chosen in 60. That is a 34% 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.