Do coding agents recommend MySQL FULLTEXT?
MySQL FULLTEXT was chosen in 2% of 876 judged search sessions, ranking number 11. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.
MySQL FULLTEXT was chosen in 2% of 876 judged search sessions, ranking number 11. It was also raised as a candidate in 24 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 search inside a realistic codebase. Not what a chat assistant says about MySQL FULLTEXT. What an agent actually installed.
One thing to read first: every one of those wins came from a single codebase. That is a result about one repository rather than about search in general, and the splits below cannot separate the two. Treat them as a description of that repository.
The numbers
| Category | Search |
| Sessions in the category | 876 |
| Sessions where MySQL FULLTEXT was chosen | 16 |
| Install share | 2% |
| Rank in category | 11 of 18 |
| Codebases it won in | 1 |
| Raised as a candidate, not chosen | 24 |
| Chosen when considered | 40% |
| Site | mysql.com |
By agent
With 16 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 MySQL FULLTEXT | Share |
|---|---|---|---|
| Claude Code | 205 | 6 | 3% |
| Codex | 261 | 1 | 0% |
| Cursor | 199 | 3 | 2% |
| Grok Build CLI | 53 | 0 | 0% |
| Muse Code | 158 | 6 | 4% |
By who was asking
MySQL FULLTEXT performs similarly across the four kinds of buyer, from 0% to 5%. That is unusual: the category leader changed with the persona in 24 of the 31 categories we measured.
| Who is asking | Sessions | Chose MySQL FULLTEXT | Share |
|---|---|---|---|
| Vibe coder | 127 | 0 | 0% |
| Junior developer | 296 | 16 | 5% |
| Senior engineer | 201 | 0 | 0% |
| Enterprise team | 252 | 0 | 0% |
What MySQL FULLTEXT was up against
The full ranking in search, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Built in-house (no product adopted) | 208 | 24% |
| 2 | Postgres Full-Text Search | 140 | 16% |
| 3 | OpenSearch | 104 | 12% |
| 4 | Typesense | 83 | 9% |
| 5 | Meilisearch | 74 | 8% |
| 6 | Oracle Indexed Search | 46 | 5% |
| 7 | Algolia | 45 | 5% |
| 8 | Elasticsearch | 42 | 5% |
What this means
MySQL FULLTEXT was raised in 24 sessions and chosen in 16. 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 876 sessions in search 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 search run can be replayed on the board.
If you work on MySQL FULLTEXT: 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 MySQL FULLTEXT?
Yes. MySQL FULLTEXT was chosen in 16 of the 876 judged sessions in search, a 2% install share, ranking number 11 in its category.
Does Claude Code recommend MySQL FULLTEXT?
In 6 of the 205 sessions in search run with Claude Code, which is 3%.
Do different coding agents treat MySQL FULLTEXT differently?
Not much. Claude Code, Codex, Cursor, Grok Build CLI and Muse Code chose it at similar rates, between 0% and 4% 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 MySQL FULLTEXT considered but not chosen?
It was raised as a candidate in 24 sessions without being chosen, and chosen in 16. That is a 40% 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.