Do coding agents recommend Algolia?
Algolia was chosen in 5% of 459 judged search sessions, ranking sixth. Measured with Claude Code, Codex and Cursor.
Algolia was chosen in 5% of 459 judged search sessions, ranking sixth. It was also raised as a candidate in 203 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 Algolia. What an agent actually installed.
The numbers
| Category | Search |
| Sessions in the category | 459 |
| Sessions where Algolia was chosen | 23 |
| Install share | 5% |
| Rank in category | 6 of 16 |
| Codebases it won in | 3 |
| Raised as a candidate, not chosen | 203 |
| Chosen when considered | 10% |
| Site | algolia.com |
By agent
The three agents agree closely on Algolia, choosing it at rates within 3 points of each other.
| Agent | Sessions | Chose Algolia | Share |
|---|---|---|---|
| Claude Code | 152 | 4 | 3% |
| Codex | 155 | 10 | 6% |
| Cursor | 152 | 9 | 6% |
By who was asking
Algolia does much better with one kind of buyer than another. It won 22% of sessions asked as senior engineer and 0% of those asked as enterprise team.
| Who is asking | Sessions | Chose Algolia | Share |
|---|---|---|---|
| Vibe coder | 65 | 0 | 0% |
| Junior developer | 193 | 0 | 0% |
| Senior engineer | 106 | 23 | 22% |
| Enterprise team | 95 | 0 | 0% |
What Algolia 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 (this page) | 23 | 5% |
| 8 | Elasticsearch | 22 | 5% |
What this means
This is an integration problem, not a presence problem. Agents raised Algolia in 203 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 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.
Every search run can be replayed on the board.
If you work on Algolia: 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 Algolia?
Yes. Algolia was chosen in 23 of the 459 judged sessions in search, a 5% install share, ranking sixth in its category.
Does Claude Code recommend Algolia?
In 4 of the 152 sessions in search run with Claude Code, which is 3%.
Do different coding agents treat Algolia differently?
Not much. The three agents chose it at similar rates, between 3% and 6% 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 Algolia considered but not chosen?
It was raised as a candidate in 203 sessions without being chosen, and chosen in 23. That is a 10% conversion from considered to chosen.
Where this comes from
Armature ran 5,292 judged sessions with Claude Code, Codex and Cursor inside 51 realistic codebases, and published every run. The numbers on this page come from that work.