# Do coding agents recommend MySQL FULLTEXT? > MySQL FULLTEXT was chosen in 2% of 459 judged search sessions, ranking tenth. Measured with Claude Code, Codex and Cursor. Source: https://armature.tech/library/do-coding-agents-recommend-mysql-fulltext Published: 2026-09-03 Publisher: Armature, Inc. (https://armature.tech) --- > MySQL FULLTEXT was chosen in 2% of 459 judged search sessions, ranking tenth. It was also raised as a candidate in 17 further sessions without being chosen. This page reports what happened when Claude Code, Codex and Cursor 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 | 459 | | Sessions where MySQL FULLTEXT was chosen | 8 | | Install share | 2% | | Rank in category | 10 of 16 | | Codebases it won in | 1 | | Raised as a candidate, not chosen | 17 | | Chosen when considered | 32% | | Site | mysql.com | ## By agent With 8 wins spread across three 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 | 152 | 4 | 3% | | Codex | 155 | 1 | 1% | | Cursor | 152 | 3 | 2% | ## By who was asking MySQL FULLTEXT performs similarly across the four kinds of buyer, from 0% to 4%. That is unusual: the category leader changed with the persona in 14 of the 18 categories we measured. | Who is asking | Sessions | Chose MySQL FULLTEXT | Share | | --- | --- | --- | --- | | Vibe coder | 65 | 0 | 0% | | Junior developer | 193 | 8 | 4% | | Senior engineer | 106 | 0 | 0% | | Enterprise team | 95 | 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) | 106 | 23% | | 2 | Postgres Full-Text Search | 79 | 17% | | 3 | OpenSearch | 59 | 13% | | 4 | Typesense | 42 | 9% | | 5 | Meilisearch | 40 | 9% | | 6 | Oracle Indexed Search | 23 | 5% | | 7 | Algolia | 23 | 5% | | 8 | Elasticsearch | 22 | 5% | ## What this means MySQL FULLTEXT was raised in 17 sessions and chosen in 8. 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 459 sessions in search are part of a published set of 5,292, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: [how we measured this](/library/how-we-measured-this). Every search run can be replayed on [the board](/leaderboards/search). 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. ## Common questions ### Do coding agents recommend MySQL FULLTEXT? Yes. MySQL FULLTEXT was chosen in 8 of the 459 judged sessions in search, a 2% install share, ranking tenth in its category. ### Does Claude Code recommend MySQL FULLTEXT? In 4 of the 152 sessions in search run with Claude Code, which is 3%. ### Do different coding agents treat MySQL FULLTEXT differently? Not much. The three agents chose it at similar rates, between 1% and 3% of their runs. ### How was this measured? Real coding agents at pinned versions were run in sandboxes inside 51 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 17 sessions without being chosen, and chosen in 8. That is a 32% conversion from considered to chosen. ## Read next - [How to get picked for search by coding agents](https://armature.tech/library/search-coding-agents-playbook) (Markdown: https://armature.tech/library/search-coding-agents-playbook.md) - [Do coding agents recommend Postgres Full-Text Search?](https://armature.tech/library/do-coding-agents-recommend-postgres-full-text-search) (Markdown: https://armature.tech/library/do-coding-agents-recommend-postgres-full-text-search.md) - [Do coding agents recommend OpenSearch?](https://armature.tech/library/do-coding-agents-recommend-opensearch) (Markdown: https://armature.tech/library/do-coding-agents-recommend-opensearch.md) - [Do Claude Code, Codex and Cursor pick the same tools?](https://armature.tech/library/do-claude-code-and-codex-agree) (Markdown: https://armature.tech/library/do-claude-code-and-codex-agree.md) --- Armature helps software products get discovered and used by coding agents. Service: https://armature.tech/discoverability · Results: https://armature.tech/leaderboards/sectors · Contact: contact@armature.tech