Do coding agents recommend Symfony Translation?
Symfony Translation was chosen in 8% of 500 judged internationalization sessions, ranking third.
Symfony Translation was chosen in 8% of 500 judged internationalization sessions, ranking third. It was also raised as a candidate in 2 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 internationalization inside a realistic codebase. Not what a chat assistant says about Symfony Translation. 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 internationalization in general, and the splits below cannot separate the two. Treat them as a description of that repository.
The numbers
| Category | Internationalization |
| Sessions in the category | 500 |
| Sessions where Symfony Translation was chosen | 41 |
| Install share | 8% |
| Rank in category | 3 of 31 |
| Codebases it won in | 1 |
| Raised as a candidate, not chosen | 2 |
| Chosen when considered | 95% |
| Site | symfony.com |
By agent
Claude Code, Codex, Cursor and Muse Code agree closely on Symfony Translation, choosing it at rates within 1 points of each other. Grok Build CLI ran fewer than 30 sessions here, too few to compare.
| Agent | Sessions | Chose Symfony Translation | Share |
|---|---|---|---|
| Claude Code | 113 | 9 | 8% |
| Codex | 150 | 12 | 8% |
| Cursor | 103 | 9 | 9% |
| Grok Build CLI | 26 | 2 | 8% |
| Muse Code | 108 | 9 | 8% |
By who was asking
Symfony Translation does much better with one kind of buyer than another. It won 16% of sessions asked as junior developer and 0% of those asked as senior engineer.
| Who is asking | Sessions | Chose Symfony Translation | Share |
|---|---|---|---|
| Vibe coder | 102 | 0 | 0% |
| Junior developer | 115 | 18 | 16% |
| Senior engineer | 113 | 0 | 0% |
| Enterprise team | 170 | 23 | 14% |
What Symfony Translation was up against
The full ranking in internationalization, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | next-intl | 110 | 22% |
| 2 | Django translation framework | 96 | 19% |
| 3 | Symfony Translation (this page) | 41 | 8% |
| 4 | Paraglide JS | 41 | 8% |
| 5 | Built in-house (no product adopted) | 41 | 8% |
| 6 | Rails I18n | 38 | 8% |
| 7 | Vue I18n | 27 | 5% |
| 8 | i18next | 27 | 5% |
What this means
Agents almost never raise Symfony Translation without choosing it: 2 sessions raised against 41 chosen. When it gets considered, it usually wins. The constraint is how rarely it gets considered at all, which is a presence problem: templates, framework integrations and pages that answer the configuration and production questions agents actually search for.
Where these numbers come from
The 500 sessions in internationalization 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 internationalization run can be replayed on the board.
If you work on Symfony Translation: 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 Symfony Translation?
Yes. Symfony Translation was chosen in 41 of the 500 judged sessions in internationalization, a 8% install share, ranking third in its category.
Does Claude Code recommend Symfony Translation?
In 9 of the 113 sessions in internationalization run with Claude Code, which is 8%.
Do different coding agents treat Symfony Translation differently?
Not much. Claude Code, Codex, Cursor and Muse Code chose it at similar rates, between 8% 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 Symfony Translation considered but not chosen?
It was raised as a candidate in 2 sessions without being chosen, and chosen in 41. That is a 95% 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.