Do coding agents recommend MapLibre?
MapLibre was chosen in 7% of 319 judged maps sessions, ranking fifth. Measured with Claude Code, Codex and Cursor.
MapLibre was chosen in 7% of 319 judged maps sessions, ranking fifth. It was also raised as a candidate in 176 further sessions without being chosen.
This page reports what happened when Claude Code, Codex and Cursor had to solve a problem in maps inside a realistic codebase. Not what a chat assistant says about MapLibre. What an agent actually installed.
The numbers
| Category | Maps |
| Sessions in the category | 319 |
| Sessions where MapLibre was chosen | 21 |
| Install share | 7% |
| Rank in category | 5 of 32 |
| Codebases it won in | 7 |
| Raised as a candidate, not chosen | 176 |
| Chosen when considered | 11% |
| Site | maplibre.org |
By agent
The three agents agree closely on MapLibre, choosing it at rates within 5 points of each other.
| Agent | Sessions | Chose MapLibre | Share |
|---|---|---|---|
| Claude Code | 108 | 10 | 9% |
| Codex | 111 | 7 | 6% |
| Cursor | 100 | 4 | 4% |
By who was asking
MapLibre does much better with one kind of buyer than another. It won 36% of sessions asked as enterprise team and 2% of those asked as vibe coder.
| Who is asking | Sessions | Chose MapLibre | Share |
|---|---|---|---|
| Vibe coder | 64 | 1 | 2% |
| Junior developer | 147 | 4 | 3% |
| Senior engineer | 72 | 3 | 4% |
| Enterprise team | 36 | 13 | 36% |
What MapLibre was up against
The full ranking in maps, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Google Maps | 52 | 16% |
| 2 | Leaflet | 52 | 16% |
| 3 | Apple Maps (MapKit) | 46 | 14% |
| 4 | Mapbox | 25 | 8% |
| 5 | MapLibre (this page) | 21 | 7% |
| 6 | react-native-maps | 19 | 6% |
| 7 | Azure Maps | 18 | 6% |
| 8 | Built in-house (no product adopted) | 16 | 5% |
What this means
This is an integration problem, not a presence problem. Agents raised MapLibre in 176 sessions and chose it in 21, so it reaches the shortlist and then loses. Something at the last step is costing the session, and in our data that is usually a quickstart that does not run when pasted, documentation describing an interface that changed, or a package name that does not match the product name.
That is the cheaper of the two problems to have. The reason is written down in each losing transcript.
Where these numbers come from
The 319 sessions in maps are part of a published set of 6,458, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every maps run can be replayed on the board.
If you work on MapLibre: 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 MapLibre?
Yes. MapLibre was chosen in 21 of the 319 judged sessions in maps, a 7% install share, ranking fifth in its category.
Does Claude Code recommend MapLibre?
In 10 of the 108 sessions in maps run with Claude Code, which is 9%.
Do different coding agents treat MapLibre differently?
Not much. The three agents chose it at similar rates, between 4% and 9% 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.
How often is MapLibre considered but not chosen?
It was raised as a candidate in 176 sessions without being chosen, and chosen in 21. That is a 11% conversion from considered to chosen.
Where this comes from
Armature ran 6,458 judged sessions with Claude Code, Codex and Cursor inside 63 realistic codebases, and published every run. The numbers on this page come from that work.