Do coding agents recommend Perplexity Sonar?
Perplexity Sonar was chosen in 4% of 639 judged AI search sessions, ranking eighth. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.
Perplexity Sonar was chosen in 4% of 639 judged AI search sessions, ranking eighth. It was also raised as a candidate in 149 further sessions without being chosen.
This page reports what happened when Claude Code, Codex, Cursor, Grok Build CLI and Muse Code had to solve a problem in AI search inside a realistic codebase. Not what a chat assistant says about Perplexity Sonar. What an agent actually installed.
The numbers
| Category | AI search |
| Sessions in the category | 639 |
| Sessions where Perplexity Sonar was chosen | 27 |
| Install share | 4% |
| Rank in category | 8 of 42 |
| Codebases it won in | 3 |
| Raised as a candidate, not chosen | 149 |
| Chosen when considered | 15% |
| Site | perplexity.ai |
By agent
Claude Code, Codex, Cursor, Grok Build CLI and Muse Code land within 8 points of each other on Perplexity Sonar, which is closer than most products in this experiment manage.
| Agent | Sessions | Chose Perplexity Sonar | Share |
|---|---|---|---|
| Claude Code | 140 | 1 | 1% |
| Codex | 192 | 9 | 5% |
| Cursor | 136 | 7 | 5% |
| Grok Build CLI | 35 | 3 | 9% |
| Muse Code | 136 | 7 | 5% |
By who was asking
Perplexity Sonar does much better with one kind of buyer than another. It won 23% of sessions asked as vibe coder and 0% of those asked as enterprise team.
| Who is asking | Sessions | Chose Perplexity Sonar | Share |
|---|---|---|---|
| Vibe coder | 106 | 24 | 23% |
| Junior developer | 208 | 2 | 1% |
| Senior engineer | 157 | 1 | 1% |
| Enterprise team | 168 | 0 | 0% |
What Perplexity Sonar was up against
The full ranking in AI search, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Exa | 92 | 14% |
| 2 | Brave Search API | 89 | 14% |
| 3 | Anthropic web search | 86 | 13% |
| 4 | Tavily | 79 | 12% |
| 5 | OpenAI web search | 32 | 5% |
| 6 | Built in-house (no product adopted) | 32 | 5% |
| 7 | Firecrawl | 31 | 5% |
| 8 | Parallel | 29 | 5% |
What this means
This is an integration problem, not a presence problem. Agents raised Perplexity Sonar in 149 sessions and chose it in 27, 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 639 sessions in AI search are part of a published set of 15,051, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every AI search run can be replayed on the board.
If you work on Perplexity Sonar: 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 Perplexity Sonar?
Yes. Perplexity Sonar was chosen in 27 of the 639 judged sessions in AI search, a 4% install share, ranking eighth in its category.
Does Claude Code recommend Perplexity Sonar?
In 1 of the 140 sessions in AI search run with Claude Code, which is 1%.
Do different coding agents treat Perplexity Sonar differently?
Not much. Claude Code, Codex, Cursor, Grok Build CLI and Muse Code chose it at similar rates, between 1% and 9% of their runs.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 92 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 Perplexity Sonar considered but not chosen?
It was raised as a candidate in 149 sessions without being chosen, and chosen in 27. That is a 15% conversion from considered to chosen.
Where this comes from
Armature ran 15,051 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 92 realistic codebases, and published every run. The numbers on this page come from that work.