From the experiment

Do coding agents recommend Retell AI?

Retell AI is the most chosen voice agent platform, taking 22% of 754 judged voice agents sessions.

Published October 14, 2026 Read as Markdown

Retell AI is the most chosen voice agent platform, taking 22% of 754 judged voice agents sessions. It was also raised as a candidate in 200 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 voice agents inside a realistic codebase. Not what a chat assistant says about Retell AI. What an agent actually installed.

The numbers

CategoryVoice agents
Sessions in the category754
Sessions where Retell AI was chosen168
Install share22%
Rank in category1 of 32
Codebases it won in10
Raised as a candidate, not chosen200
Chosen when considered46%
Siteretellai.com

By agent

Claude Code, Codex, Cursor, Grok Build CLI and Muse Code land within 14 points of each other on Retell AI, which is closer than most products in this experiment manage.

AgentSessionsChose Retell AIShare
Claude Code1572516%
Codex2176429%
Cursor1672917%
Grok Build CLI60915%
Muse Code1534127%

By who was asking

Retell AI does much better with one kind of buyer than another. It won 50% of sessions asked as vibe coder and 6% of those asked as enterprise team.

Who is askingSessionsChose Retell AIShare
Vibe coder1346750%
Junior developer902224%
Senior engineer3226721%
Enterprise team208126%

What Retell AI was up against

The full ranking in voice agents, from the same sessions:

#ProductRuns wonShare
1Retell AI (this page)16822%
2Vapi12416%
3Twilio ConversationRelay9913%
4LiveKit Agents9813%
5ElevenLabs Agents598%
6OpenAI Realtime API496%
7Built in-house (no product adopted)355%
8Grok Voice Think Fast 2.0294%

What this means

Leading a category is a position to defend rather than a result to celebrate. In our data, leaders lose ground in exactly two situations: when the person asking is an enterprise buyer with procurement constraints, and when a competitor's documentation is easier for an agent to integrate correctly.

The defence is unglamorous. Keep the quickstart running. Keep the version current on the page. Keep the names aligned. Stay in the templates.

Where these numbers come from

The 754 sessions in voice agents 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 voice agents run can be replayed on the board.

If you work on Retell AI: 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 Retell AI?

Yes. Retell AI was chosen in 168 of the 754 judged sessions in voice agents, a 22% install share, ranking first in its category.

Does Claude Code recommend Retell AI?

In 25 of the 157 sessions in voice agents run with Claude Code, which is 16%.

Do different coding agents treat Retell AI differently?

Yes, and by a wide margin. Codex chose it in 29% of its runs and Grok Build CLI in 15%.

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.

How often is Retell AI considered but not chosen?

It was raised as a candidate in 200 sessions without being chosen, and chosen in 168. That is a 46% conversion from considered to chosen.

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.

Read next

All library pages