Do coding agents recommend Daily?
Daily was chosen in 16% of 175 judged in-app chat and calls sessions, ranking third. Measured with Claude Code, Codex and Cursor.
Daily was chosen in 16% of 175 judged in-app chat and calls sessions, ranking third. It was also raised as a candidate in 63 further sessions without being chosen.
This page reports what happened when Claude Code, Codex and Cursor had to solve a problem in in-app chat and calls inside a realistic codebase. Not what a chat assistant says about Daily. What an agent actually installed.
The numbers
| Category | In-app chat and calls |
| Sessions in the category | 175 |
| Sessions where Daily was chosen | 28 |
| Install share | 16% |
| Rank in category | 3 of 17 |
| Codebases it won in | 2 |
| Raised as a candidate, not chosen | 63 |
| Chosen when considered | 31% |
| Site | daily.co |
By agent
The three agents agree closely on Daily, choosing it at rates within 5 points of each other.
| Agent | Sessions | Chose Daily | Share |
|---|---|---|---|
| Claude Code | 71 | 11 | 15% |
| Codex | 72 | 13 | 18% |
| Cursor | 32 | 4 | 13% |
By who was asking
Daily does much better with one kind of buyer than another. It won 47% of sessions asked as junior developer and 0% of those asked as enterprise team.
| Who is asking | Sessions | Chose Daily | Share |
|---|---|---|---|
| Vibe coder | 60 | 1 | 2% |
| Junior developer | 58 | 27 | 47% |
| Senior engineer | 29 | 0 | 0% |
| Enterprise team | 28 | 0 | 0% |
What Daily was up against
The full ranking in in-app chat and calls, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Stream Chat and Video | 52 | 30% |
| 2 | Supabase | 30 | 17% |
| 3 | Daily (this page) | 28 | 16% |
| 4 | LiveKit | 13 | 7% |
| 5 | TalkJS | 11 | 6% |
| 6 | Ably + LiveKit | 8 | 5% |
| 7 | Daily + Stream Chat and Video | 7 | 4% |
| 8 | Twilio | 7 | 4% |
What this means
A solid second or third position in a category means the agent is genuinely choosing rather than reaching automatically. That is a winnable position, because the inputs it uses can be changed.
The fastest gains are usually in the sessions that were nearly won: read them, find the step where the agent moved on, and fix that step.
Where these numbers come from
The 175 sessions in in-app chat and calls are part of a published set of 5,915, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every in-app chat and calls run can be replayed on the board.
If you work on Daily: 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 Daily?
Yes. Daily was chosen in 28 of the 175 judged sessions in in-app chat and calls, a 16% install share, ranking third in its category.
Does Claude Code recommend Daily?
In 11 of the 71 sessions in in-app chat and calls run with Claude Code, which is 15%.
Do different coding agents treat Daily differently?
Not much. The three agents chose it at similar rates, between 13% and 18% of their runs.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 56 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 Daily considered but not chosen?
It was raised as a candidate in 63 sessions without being chosen, and chosen in 28. That is a 31% conversion from considered to chosen.
Where this comes from
Armature ran 5,915 judged sessions with Claude Code, Codex and Cursor inside 56 realistic codebases, and published every run. The numbers on this page come from that work.