Do coding agents recommend Google Identity?
Google Identity was chosen in 2% of 656 judged authentication sessions, ranking ninth. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.
Google Identity was chosen in 2% of 656 judged authentication sessions, ranking ninth. It was also raised as a candidate in 64 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 authentication inside a realistic codebase. Not what a chat assistant says about Google Identity. What an agent actually installed.
The numbers
| Category | Authentication |
| Sessions in the category | 656 |
| Sessions where Google Identity was chosen | 10 |
| Install share | 2% |
| Rank in category | 9 of 28 |
| Codebases it won in | 2 |
| Raised as a candidate, not chosen | 64 |
| Chosen when considered | 14% |
| Site | developers.google.com |
By agent
With 10 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 Identity | Share |
|---|---|---|---|
| Claude Code | 133 | 0 | 0% |
| Codex | 136 | 3 | 2% |
| Cursor | 133 | 4 | 3% |
| Grok Build CLI | 50 | 0 | 0% |
| Muse Code | 204 | 3 | 1% |
By who was asking
Google Identity performs similarly across the four kinds of buyer, from 0% to 11%. That is unusual: the category leader changed with the persona in 22 of the 29 categories we measured.
| Who is asking | Sessions | Chose Google Identity | Share |
|---|---|---|---|
| Vibe coder | 89 | 10 | 11% |
| Junior developer | 202 | 0 | 0% |
| Senior engineer | 220 | 0 | 0% |
| Enterprise team | 145 | 0 | 0% |
What Google Identity was up against
The full ranking in authentication, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Auth0 | 157 | 24% |
| 2 | WorkOS AuthKit | 125 | 19% |
| 3 | Clerk | 78 | 12% |
| 4 | Microsoft Entra ID | 73 | 11% |
| 5 | Built in-house (no product adopted) | 60 | 9% |
| 6 | Better Auth | 26 | 4% |
| 7 | Amazon Cognito | 20 | 3% |
| 8 | Keycloak | 19 | 3% |
What this means
This is an integration problem, not a presence problem. Agents raised Google Identity in 64 sessions and chose it in 10, 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 656 sessions in authentication are part of a published set of 13,497, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every authentication run can be replayed on the board.
If you work on Google Identity: 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 Identity?
Yes. Google Identity was chosen in 10 of the 656 judged sessions in authentication, a 2% install share, ranking ninth in its category.
Does Claude Code recommend Google Identity?
In 0 of the 133 sessions in authentication run with Claude Code, which is 0%.
Do different coding agents treat Google Identity differently?
Not much. Claude Code, Codex, Cursor, Grok Build CLI and Muse Code chose it at similar rates, between 0% and 3% of their runs.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 91 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 Identity considered but not chosen?
It was raised as a candidate in 64 sessions without being chosen, and chosen in 10. That is a 14% conversion from considered to chosen.
Where this comes from
Armature ran 13,497 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 91 realistic codebases, and published every run. The numbers on this page come from that work.