Do coding agents recommend Better Auth?
Better Auth was chosen in 4% of 724 judged authentication sessions, ranking fifth. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.
Better Auth was chosen in 4% of 724 judged authentication sessions, ranking fifth. 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 Better Auth. What an agent actually installed.
The numbers
| Category | Authentication |
| Sessions in the category | 724 |
| Sessions where Better Auth was chosen | 29 |
| Install share | 4% |
| Rank in category | 5 of 28 |
| Codebases it won in | 3 |
| Raised as a candidate, not chosen | 64 |
| Chosen when considered | 31% |
| Site | better-auth.com |
By agent
Claude Code, Codex, Cursor, Grok Build CLI and Muse Code agree closely on Better Auth, choosing it at rates within 5 points of each other.
| Agent | Sessions | Chose Better Auth | Share |
|---|---|---|---|
| Claude Code | 133 | 6 | 5% |
| Codex | 204 | 8 | 4% |
| Cursor | 133 | 7 | 5% |
| Grok Build CLI | 50 | 0 | 0% |
| Muse Code | 204 | 8 | 4% |
By who was asking
Better Auth performs similarly across the four kinds of buyer, from 0% to 9%. That is unusual: the category leader changed with the persona in 24 of the 31 categories we measured.
| Who is asking | Sessions | Chose Better Auth | Share |
|---|---|---|---|
| Vibe coder | 98 | 0 | 0% |
| Junior developer | 223 | 19 | 9% |
| Senior engineer | 243 | 10 | 4% |
| Enterprise team | 160 | 0 | 0% |
What Better Auth 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 (this page) | 29 | 4% |
| 7 | Amazon Cognito | 23 | 3% |
| 8 | Keycloak | 22 | 3% |
What this means
Better Auth was raised in 64 sessions and chosen in 29. That ratio is balanced enough that the ceiling is presence rather than integration: the product converts reasonably when it is on the table, and it is not on the table often enough.
Where these numbers come from
The 724 sessions in authentication 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 authentication run can be replayed on the board.
If you work on Better Auth: 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 Better Auth?
Yes. Better Auth was chosen in 29 of the 724 judged sessions in authentication, a 4% install share, ranking fifth in its category.
Does Claude Code recommend Better Auth?
In 6 of the 133 sessions in authentication run with Claude Code, which is 5%.
Do different coding agents treat Better Auth differently?
Not much. Claude Code, Codex, Cursor, Grok Build CLI 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 Better Auth considered but not chosen?
It was raised as a candidate in 64 sessions without being chosen, and chosen in 29. That is a 31% 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.