Do coding agents recommend Solr?
Coding agents raised Solr in 78 of 876 judged search sessions and chose it in none of them.
Coding agents raised Solr in 78 of 876 judged search sessions and chose it in none of them.
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 Solr. What an agent actually installed.
The numbers
| Category | Search |
| Sessions in the category | 876 |
| Sessions where Solr was chosen | 0 |
| Install share | 0% |
| Raised as a candidate, not chosen | 78 |
| Chosen when considered | 0% |
| Site | solr.apache.org |
Which agents raised Solr
Every agent considered it and none adopted it. Cursor raised it most often, in 26% of its search sessions.
| Agent | Sessions | Raised Solr | Chose it |
|---|---|---|---|
| Claude Code | 205 | 20 (10%) | 0 |
| Codex | 261 | 3 (1%) | 0 |
| Cursor | 199 | 51 (26%) | 0 |
| Grok Build CLI | 53 | 1 (2%) | 0 |
| Muse Code | 158 | 3 (2%) | 0 |
Which buyers it came up for
It surfaced most for requests written as enterprise team, in 20% 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 | 127 | 0 (0%) |
| Junior developer | 296 | 21 (7%) |
| Senior engineer | 201 | 6 (3%) |
| Enterprise team | 252 | 51 (20%) |
What Solr 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
Raised 78 times and chosen none is a specific, diagnosable result, and a better starting position than being unknown. The agent has the product in mind. It reached the shortlist 78 times. Something then lost every one of those sessions.
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 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 Solr: 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 Solr?
They raise it but do not choose it. Across 78 sessions where Solr came up as a candidate, agents chose something else every time.
Does Claude Code recommend Solr?
In 0 of the 205 sessions in search run with Claude Code, which is 0%.
Do different coding agents treat Solr differently?
Not much. Claude Code, Codex, Cursor, Grok Build CLI and Muse Code 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.