Do coding agents recommend TalkJS?
TalkJS was chosen in 6% of 175 judged in-app chat and calls sessions, ranking fifth. Measured with Claude Code, Codex and Cursor.
TalkJS was chosen in 6% of 175 judged in-app chat and calls sessions, ranking fifth. It was also raised as a candidate in 11 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 TalkJS. 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 in-app chat and calls in general, and the splits below cannot separate the two. Treat them as a description of that repository.
The numbers
| Category | In-app chat and calls |
| Sessions in the category | 175 |
| Sessions where TalkJS was chosen | 11 |
| Install share | 6% |
| Rank in category | 5 of 17 |
| Codebases it won in | 1 |
| Raised as a candidate, not chosen | 11 |
| Chosen when considered | 50% |
| Site | talkjs.com |
By agent
With 11 wins spread across three agents, the rates below are small numbers and a difference between them is not yet a finding. They are here because the direction is worth knowing, not because the gap is established.
| Agent | Sessions | Chose TalkJS | Share |
|---|---|---|---|
| Claude Code | 71 | 4 | 6% |
| Codex | 72 | 5 | 7% |
| Cursor | 32 | 2 | 6% |
By who was asking
TalkJS does much better with one kind of buyer than another. It won 19% of sessions asked as junior developer and 0% of those asked as enterprise team.
| Who is asking | Sessions | Chose TalkJS | Share |
|---|---|---|---|
| Vibe coder | 60 | 0 | 0% |
| Junior developer | 58 | 11 | 19% |
| Senior engineer | 29 | 0 | 0% |
| Enterprise team | 28 | 0 | 0% |
What TalkJS 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 | 28 | 16% |
| 4 | LiveKit | 13 | 7% |
| 5 | TalkJS (this page) | 11 | 6% |
| 6 | Ably + LiveKit | 8 | 5% |
| 7 | Daily + Stream Chat and Video | 7 | 4% |
| 8 | Twilio | 7 | 4% |
What this means
TalkJS was raised in 11 sessions and chosen in 11. 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 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 TalkJS: 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 TalkJS?
Yes. TalkJS was chosen in 11 of the 175 judged sessions in in-app chat and calls, a 6% install share, ranking fifth in its category.
Does Claude Code recommend TalkJS?
In 4 of the 71 sessions in in-app chat and calls run with Claude Code, which is 6%.
Do different coding agents treat TalkJS differently?
Not much. The three agents chose it at similar rates, between 6% and 7% 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 TalkJS considered but not chosen?
It was raised as a candidate in 11 sessions without being chosen, and chosen in 11. That is a 50% 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.