Do coding agents recommend Google Cloud Run?
Google Cloud Run was chosen in 3% of 476 judged serverless compute sessions, ranking fifth.
Google Cloud Run was chosen in 3% of 476 judged serverless compute sessions, ranking fifth. It was also raised as a candidate in 74 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 serverless compute inside a realistic codebase. Not what a chat assistant says about Google Cloud Run. What an agent actually installed.
The numbers
| Category | Serverless compute |
| Sessions in the category | 476 |
| Sessions where Google Cloud Run was chosen | 14 |
| Install share | 3% |
| Rank in category | 5 of 14 |
| Codebases it won in | 2 |
| Raised as a candidate, not chosen | 74 |
| Chosen when considered | 16% |
| Site | cloud.google.com |
By agent
With 14 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 Google Cloud Run | Share |
|---|---|---|---|
| Claude Code | 120 | 6 | 5% |
| Codex | 144 | 5 | 3% |
| Cursor | 119 | 3 | 3% |
| Grok Build CLI | 22 | 0 | 0% |
| Muse Code | 71 | 0 | 0% |
By who was asking
Google Cloud Run performs similarly across the four kinds of buyer, from 0% to 7%. That is unusual: the category leader changed with the persona in 24 of the 31 categories we measured.
| Who is asking | Sessions | Chose Google Cloud Run | Share |
|---|---|---|---|
| Vibe coder | 60 | 0 | 0% |
| Junior developer | 119 | 8 | 7% |
| Senior engineer | 177 | 6 | 3% |
| Enterprise team | 120 | 0 | 0% |
What Google Cloud Run was up against
The full ranking in serverless compute, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | AWS Lambda | 114 | 24% |
| 2 | Vercel Functions | 110 | 23% |
| 3 | Built in-house (no product adopted) | 88 | 18% |
| 4 | Azure Functions | 59 | 12% |
| 5 | Cloudflare Workers | 30 | 6% |
| 6 | Google Cloud Run (this page) | 14 | 3% |
| 7 | Inngest | 8 | 2% |
| 8 | Fly.io | 8 | 2% |
What this means
This is an integration problem, not a presence problem. Agents raised Google Cloud Run in 74 sessions and chose it in 14, 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 476 sessions in serverless compute 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 serverless compute run can be replayed on the board.
If you work on Google Cloud Run: 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 Run?
Yes. Google Cloud Run was chosen in 14 of the 476 judged sessions in serverless compute, a 3% install share, ranking fifth in its category.
Does Claude Code recommend Google Cloud Run?
In 6 of the 120 sessions in serverless compute run with Claude Code, which is 5%.
Do different coding agents treat Google Cloud Run differently?
Not much. Claude Code, Codex, Cursor and Muse Code chose it at similar rates, between 0% and 5% 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 Run considered but not chosen?
It was raised as a candidate in 74 sessions without being chosen, and chosen in 14. That is a 16% 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.