# Do coding agents recommend Oracle Indexed Search?

> Oracle Indexed Search was chosen in 5% of 459 judged search sessions, ranking fifth. Measured with Claude Code, Codex and Cursor.

Source: https://armature.tech/library/do-coding-agents-recommend-oracle-indexed-search
Published: 2026-09-03
Publisher: Armature, Inc. (https://armature.tech)

---

> Oracle Indexed Search was chosen in 5% of 459 judged search sessions, ranking fifth.

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 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 | 459 |
| Sessions where Oracle Indexed Search was chosen | 23 |
| Install share | 5% |
| Rank in category | 5 of 16 |
| Codebases it won in | 1 |
| Raised as a candidate, not chosen | 0 |
| Chosen when considered | 100% |
| Site | oracle.com |

## By agent

The three agents agree closely on Oracle Indexed Search, choosing it at rates within 2 points of each other.

| Agent | Sessions | Chose Oracle Indexed Search | Share |
| --- | --- | --- | --- |
| Claude Code | 152 | 8 | 5% |
| Codex | 155 | 6 | 4% |
| Cursor | 152 | 9 | 6% |

## 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 | 65 | 0 | 0% |
| Junior developer | 193 | 9 | 5% |
| Senior engineer | 106 | 0 | 0% |
| Enterprise team | 95 | 14 | 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) | 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 **(this page)** | 23 | 5% |
| 7 | Algolia | 23 | 5% |
| 8 | Elasticsearch | 22 | 5% |

## What this means

Agents almost never raise Oracle Indexed Search without choosing it: 0 sessions raised against 23 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 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 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 23 of the 459 judged sessions in search, a 5% install share, ranking fifth in its category.

### Does Claude Code recommend Oracle Indexed Search?

In 8 of the 152 sessions in search run with Claude Code, which is 5%.

### Do different coding agents treat Oracle Indexed Search differently?

Not much. The three agents chose it at similar rates, between 4% 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.

## 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
