Do coding agents recommend Oracle Indexed Search?
Oracle Indexed Search was chosen in 5% of 876 judged search sessions, ranking fifth. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.
Oracle Indexed Search was chosen in 5% of 876 judged search sessions, ranking fifth.
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 Oracle Indexed Search. 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 Oracle Indexed Search was chosen | 46 |
| Install share | 5% |
| Rank in category | 5 of 18 |
| Codebases it won in | 1 |
| Raised as a candidate, not chosen | 0 |
| Chosen when considered | 100% |
| Site | oracle.com |
By agent
Claude Code, Codex, Cursor, Grok Build CLI and Muse Code agree closely on Oracle Indexed Search, choosing it at rates within 3 points of each other.
| Agent | Sessions | Chose Oracle Indexed Search | Share |
|---|---|---|---|
| Claude Code | 205 | 12 | 6% |
| Codex | 261 | 10 | 4% |
| Cursor | 199 | 11 | 6% |
| Grok Build CLI | 53 | 2 | 4% |
| Muse Code | 158 | 11 | 7% |
By who was asking
Oracle Indexed Search does much better with one kind of buyer than another. It won 15% of sessions asked as enterprise team and 0% of those asked as senior engineer.
| Who is asking | Sessions | Chose Oracle Indexed Search | Share |
|---|---|---|---|
| Vibe coder | 127 | 0 | 0% |
| Junior developer | 296 | 9 | 3% |
| Senior engineer | 201 | 0 | 0% |
| Enterprise team | 252 | 37 | 15% |
What Oracle Indexed Search 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 (this page) | 46 | 5% |
| 7 | Algolia | 45 | 5% |
| 8 | Elasticsearch | 42 | 5% |
What this means
Agents almost never raise Oracle Indexed Search without choosing it: 0 sessions raised against 46 chosen. When it gets considered, it usually wins. The constraint is how rarely it gets considered at all, which is a presence problem: templates, framework integrations and pages that answer the configuration and production questions agents actually search for.
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 Oracle Indexed Search: 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 Oracle Indexed Search?
Yes. Oracle Indexed Search was chosen in 46 of the 876 judged sessions in search, a 5% install share, ranking fifth in its category.
Does Claude Code recommend Oracle Indexed Search?
In 12 of the 205 sessions in search run with Claude Code, which is 6%.
Do different coding agents treat Oracle Indexed Search differently?
Not much. Claude Code, Codex, Cursor, Grok Build CLI and Muse Code chose it at similar rates, between 4% and 7% 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.