Do coding agents recommend Amazon Cognito?
Amazon Cognito was chosen in 3% of 724 judged authentication sessions, ranking sixth. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.
Amazon Cognito was chosen in 3% of 724 judged authentication sessions, ranking sixth. It was also raised as a candidate in 231 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 Amazon Cognito. What an agent actually installed.
The numbers
| Category | Authentication |
| Sessions in the category | 724 |
| Sessions where Amazon Cognito was chosen | 23 |
| Install share | 3% |
| Rank in category | 6 of 28 |
| Codebases it won in | 3 |
| Raised as a candidate, not chosen | 231 |
| Chosen when considered | 9% |
| Site | aws.amazon.com |
By agent
Claude Code, Codex, Cursor, Grok Build CLI and Muse Code land within 7 points of each other on Amazon Cognito, which is closer than most products in this experiment manage.
| Agent | Sessions | Chose Amazon Cognito | Share |
|---|---|---|---|
| Claude Code | 133 | 0 | 0% |
| Codex | 204 | 4 | 2% |
| Cursor | 133 | 4 | 3% |
| Grok Build CLI | 50 | 0 | 0% |
| Muse Code | 204 | 15 | 7% |
By who was asking
Amazon Cognito performs similarly across the four kinds of buyer, from 0% to 9%. That is unusual: the category leader changed with the persona in 23 of the 31 categories we measured.
| Who is asking | Sessions | Chose Amazon Cognito | Share |
|---|---|---|---|
| Vibe coder | 98 | 0 | 0% |
| Junior developer | 223 | 0 | 0% |
| Senior engineer | 243 | 9 | 4% |
| Enterprise team | 160 | 14 | 9% |
What Amazon Cognito was up against
The full ranking in authentication, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Auth0 | 180 | 25% |
| 2 | WorkOS AuthKit | 131 | 18% |
| 3 | Clerk | 86 | 12% |
| 4 | Microsoft Entra ID | 80 | 11% |
| 5 | Built in-house (no product adopted) | 65 | 9% |
| 6 | Better Auth | 29 | 4% |
| 7 | Amazon Cognito (this page) | 23 | 3% |
| 8 | Keycloak | 22 | 3% |
What this means
This is an integration problem, not a presence problem. Agents raised Amazon Cognito in 231 sessions and chose it in 23, 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 724 sessions in authentication 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 authentication run can be replayed on the board.
If you work on Amazon Cognito: 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 Cognito?
Yes. Amazon Cognito was chosen in 23 of the 724 judged sessions in authentication, a 3% install share, ranking sixth in its category.
Does Claude Code recommend Amazon Cognito?
In 0 of the 133 sessions in authentication run with Claude Code, which is 0%.
Do different coding agents treat Amazon Cognito differently?
Not much. Claude Code, Codex, Cursor, Grok Build CLI and Muse Code chose it at similar rates, between 0% and 7% 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 Cognito considered but not chosen?
It was raised as a candidate in 231 sessions without being chosen, and chosen in 23. That is a 9% 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.