# Do coding agents recommend Weblate?

> Coding agents raised Weblate in 79 of 224 judged internationalization sessions and chose it in none of them. Measured with Claude Code, Codex and Cursor.

Source: https://armature.tech/library/do-coding-agents-recommend-weblate
Published: 2026-09-11
Publisher: Armature, Inc. (https://armature.tech)

---

> Coding agents raised Weblate in 79 of 224 judged internationalization sessions and chose it in none of them.

This page reports what happened when Claude Code, Codex and Cursor had to solve a problem in internationalization inside a realistic codebase. Not what a chat assistant says about Weblate. What an agent actually installed.

## The numbers

| | |
| --- | --- |
| Category | Internationalization |
| Sessions in the category | 224 |
| Sessions where Weblate was chosen | 0 |
| Install share | 0% |
| Raised as a candidate, not chosen | 79 |
| Chosen when considered | 0% |
| Site | weblate.org |

## Which agents raised Weblate

Every agent considered it and none adopted it. Cursor raised it most often, in 51% of its internationalization sessions.

| Agent | Sessions | Raised Weblate | Chose it |
| --- | --- | --- | --- |
| Claude Code | 77 | 27 (35%) | 0 |
| Codex | 78 | 17 (22%) | 0 |
| Cursor | 69 | 35 (51%) | 0 |

## Which buyers it came up for

It surfaced most for requests written as enterprise team, in 67% of those sessions. Knowing which buyer already has the product in mind tells you which pages to fix first.

| Who is asking | Sessions | Raised it |
| --- | --- | --- |
| Vibe coder | 54 | 6 (11%) |
| Junior developer | 69 | 32 (46%) |
| Senior engineer | 47 | 5 (11%) |
| Enterprise team | 54 | 36 (67%) |

## What Weblate was up against

The full ranking in internationalization, from the same sessions:

| # | Product | Runs won | Share |
| --- | --- | --- | --- |
| 1 | next-intl | 57 | 25% |
| 2 | Django translation framework | 45 | 20% |
| 3 | Symfony Translation | 18 | 8% |
| 4 | Paraglide JS | 18 | 8% |
| 5 | Rails I18n | 17 | 8% |
| 6 | i18next | 14 | 6% |
| 7 | Built in-house (no product adopted) | 12 | 5% |
| 8 | Vue I18n | 10 | 4% |

## What this means

Raised 79 times and chosen none is a specific, diagnosable result, and a better starting position than being unknown. The agent has the product in mind. It reached the shortlist 79 times. Something then lost every one of those sessions.

In our data the causes, in the order they occur:

- The quickstart does not run when pasted, so the agent abandoned it mid-integration.
- The documentation describes an interface that changed, so the generated code failed.
- The product name and the package name differ, so the install step went wrong.
- The fit was genuinely wrong for the repository, which is fine and worth knowing.

All but the last are fixable in days, and the reason is written down in the session transcript.

## Where these numbers come from

The 224 sessions in internationalization are part of a published set of 6,455, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: [how we measured this](/library/how-we-measured-this).

Every internationalization run can be replayed on [the board](/leaderboards/internationalization).

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

They raise it but do not choose it. Across 79 sessions where Weblate came up as a candidate, agents chose something else every time.

### Does Claude Code recommend Weblate?

In 0 of the 77 sessions in internationalization run with Claude Code, which is 0%.

### Do different coding agents treat Weblate differently?

Not much. The three agents chose it at similar rates, between 0% and 0% of their runs.

### How was this measured?

Real coding agents at pinned versions were run in sandboxes inside 63 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.

## Read next

- [How to get picked for internationalization by coding agents](https://armature.tech/library/internationalization-coding-agents-playbook) (Markdown: https://armature.tech/library/internationalization-coding-agents-playbook.md)
- [Do coding agents recommend next-intl?](https://armature.tech/library/do-coding-agents-recommend-next-intl) (Markdown: https://armature.tech/library/do-coding-agents-recommend-next-intl.md)
- [Do coding agents recommend Django translation framework?](https://armature.tech/library/do-coding-agents-recommend-django-translation-framework) (Markdown: https://armature.tech/library/do-coding-agents-recommend-django-translation-framework.md)
- [Do Claude Code, Codex and Cursor pick the same tools?](https://armature.tech/library/do-claude-code-and-codex-agree) (Markdown: https://armature.tech/library/do-claude-code-and-codex-agree.md)

---

Armature helps software products get discovered and used by coding agents.
Service: https://armature.tech/discoverability · Results: https://armature.tech/leaderboards/sectors · Contact: contact@armature.tech