Do coding agents recommend SQLite?
SQLite came up in 72% of judged databases sessions and was adopted in none: on this board it is substrate, not a candidate.
SQLite came up in 72% of judged databases sessions and was adopted in none: on this board it is substrate, not a candidate.
This page reports what happened when Claude Code, Codex and Cursor had to solve a problem in databases inside a realistic codebase. Not what a chat assistant says about SQLite. What an agent actually installed.
The numbers
| Category | Databases |
| Sessions in the category | 732 |
| Sessions where SQLite was chosen | 0 |
| Install share | 0% |
| Raised as a candidate, not chosen | 524 |
| Chosen when considered | 0% |
| Site | sqlite.org |
Which agents raised SQLite
SQLite came up in 72% of databases sessions and was chosen alone in none. At that rate it is not a candidate that keeps losing: it is the thing already in the repository, or the standard the alternatives get measured against. Cursor named it in 89% of its sessions.
| Agent | Sessions | Raised SQLite | Chose it alone |
|---|---|---|---|
| Claude Code | 380 | 295 (78%) | 0 |
| Codex | 181 | 77 (43%) | 0 |
| Cursor | 171 | 152 (89%) | 0 |
Which buyers it came up for
It surfaced most for requests written as senior engineer, in 81% of those sessions. Knowing which buyer already has the product in mind tells you which pages to fix first.
| Who is asking | Sessions | Raised it |
|---|---|---|
| Vibe coder | 417 | 278 (67%) |
| Junior developer | 163 | 124 (76%) |
| Senior engineer | 113 | 91 (81%) |
| Enterprise team | 24 | 18 (75%) |
What SQLite was up against
The full ranking in databases, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Neon | 334 | 46% |
| 2 | Supabase | 269 | 37% |
| 3 | Turso | 48 | 7% |
| 4 | Azure Database for PostgreSQL Flexible Server | 21 | 3% |
| 5 | Firebase | 17 | 2% |
| 6 | Google Sheets | 10 | 1% |
| 7 | Netlify Forms | 6 | 1% |
| 8 | Formspree | 4 | 1% |
What this means
Read this row as context, not as a loss. On this board SQLite is the thing underneath rather than one of the candidates: the database already in the repository, the protocol the alternatives implement, or the runtime they all run on. Our judge has an explicit rule for the clearest case: a vendor-neutral standard is never recorded as the winner, because it is the wiring and not the destination.
Where that reading does not apply, the causes below are the ones we see.
In our data the causes, in the order they occur:
- The quickstart does not run when pasted, so the agent abandoned it mid-integration.
- The documentation describes an interface that changed, so the generated code failed.
- The product name and the package name differ, so the install step went wrong.
- The fit was genuinely wrong for the repository, which is fine and worth knowing.
All but the last are fixable in days, and the reason is written down in the session transcript.
Where these numbers come from
The 732 sessions in databases 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 databases run can be replayed on the board.
If you work on SQLite: 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 SQLite?
They raise it but rarely choose it. Across 524 sessions where SQLite came up as a candidate, agents never chose it alone; it was part of a joint choice in 1.
Does Claude Code recommend SQLite?
In 0 of the 380 sessions in databases run with Claude Code, which is 0%.
Do different coding agents treat SQLite differently?
Not much. Claude Code, Codex and Cursor chose it at similar rates, between 0% and 0% 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.
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.