Do coding agents recommend Parallel?
Parallel was chosen in 5% of 639 judged AI search sessions, ranking seventh. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.
Parallel was chosen in 5% of 639 judged AI search sessions, ranking seventh. It was also raised as a candidate in 35 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 Parallel. What an agent actually installed.
The numbers
| Category | AI search |
| Sessions in the category | 639 |
| Sessions where Parallel was chosen | 29 |
| Install share | 5% |
| Rank in category | 7 of 42 |
| Codebases it won in | 6 |
| Raised as a candidate, not chosen | 35 |
| Chosen when considered | 45% |
| Site | parallel.ai |
By agent
Claude Code, Codex, Cursor, Grok Build CLI and Muse Code land within 10 points of each other on Parallel, which is closer than most products in this experiment manage.
| Agent | Sessions | Chose Parallel | Share |
|---|---|---|---|
| Claude Code | 140 | 1 | 1% |
| Codex | 192 | 14 | 7% |
| Cursor | 136 | 14 | 10% |
| Grok Build CLI | 35 | 0 | 0% |
| Muse Code | 136 | 0 | 0% |
By who was asking
Parallel performs similarly across the four kinds of buyer, from 0% to 14%. That is unusual: the category leader changed with the persona in 23 of the 31 categories we measured.
| Who is asking | Sessions | Chose Parallel | Share |
|---|---|---|---|
| Vibe coder | 106 | 0 | 0% |
| Junior developer | 208 | 4 | 2% |
| Senior engineer | 157 | 22 | 14% |
| Enterprise team | 168 | 3 | 2% |
What Parallel 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 (this page) | 29 | 5% |
What this means
Parallel was raised in 35 sessions and chosen in 29. That ratio is balanced enough that the ceiling is presence rather than integration: the product converts reasonably when it is on the table, and it is not on the table often enough.
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 Parallel: 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 Parallel?
Yes. Parallel was chosen in 29 of the 639 judged sessions in AI search, a 5% install share, ranking seventh in its category.
Does Claude Code recommend Parallel?
In 1 of the 140 sessions in AI search run with Claude Code, which is 1%.
Do different coding agents treat Parallel differently?
Yes, and by a wide margin. Cursor chose it in 10% of its runs and Grok Build CLI in 0%.
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 Parallel considered but not chosen?
It was raised as a candidate in 35 sessions without being chosen, and chosen in 29. That is a 45% 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.