Do coding agents recommend MapLibre?
MapLibre was chosen in 8% of 759 judged maps sessions, ranking fourth. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.
MapLibre was chosen in 8% of 759 judged maps sessions, ranking fourth. It was also raised as a candidate in 297 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 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 | 759 |
| Sessions where MapLibre was chosen | 61 |
| Install share | 8% |
| Rank in category | 4 of 49 |
| Codebases it won in | 10 |
| Raised as a candidate, not chosen | 297 |
| Chosen when considered | 17% |
| Site | maplibre.org |
By agent
The agents treat MapLibre very differently. Grok Build CLI chose it in 22% of its sessions in this category and Cursor in 6%, a spread of 16 points.
| Agent | Sessions | Chose MapLibre | Share |
|---|---|---|---|
| Claude Code | 164 | 13 | 8% |
| Codex | 227 | 16 | 7% |
| Cursor | 154 | 10 | 6% |
| Grok Build CLI | 37 | 8 | 22% |
| Muse Code | 177 | 14 | 8% |
A single blended install share would report the midpoint and hide both ends. If most of your users run Cursor, your real position here is 6%, not 8%.
By who was asking
MapLibre does much better with one kind of buyer than another. It won 24% of sessions asked as enterprise team and 2% of those asked as senior engineer.
| Who is asking | Sessions | Chose MapLibre | Share |
|---|---|---|---|
| Vibe coder | 163 | 8 | 5% |
| Junior developer | 247 | 5 | 2% |
| Senior engineer | 162 | 4 | 2% |
| Enterprise team | 187 | 44 | 24% |
What MapLibre was up against
The full ranking in maps, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Google Maps | 133 | 18% |
| 2 | Leaflet | 125 | 16% |
| 3 | Apple Maps (MapKit) | 104 | 14% |
| 4 | MapLibre (this page) | 61 | 8% |
| 5 | Mapbox | 52 | 7% |
| 6 | Built in-house (no product adopted) | 43 | 6% |
| 7 | react-native-maps | 37 | 5% |
| 8 | OpenStreetMap | 37 | 5% |
What this means
This is an integration problem, not a presence problem. Agents raised MapLibre in 297 sessions and chose it in 61, 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 759 sessions in maps 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 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 61 of the 759 judged sessions in maps, a 8% install share, ranking fourth in its category.
Does Claude Code recommend MapLibre?
In 13 of the 164 sessions in maps run with Claude Code, which is 8%.
Do different coding agents treat MapLibre differently?
Yes, and by a wide margin. Grok Build CLI chose it in 22% of its runs and Cursor in 6%.
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 MapLibre considered but not chosen?
It was raised as a candidate in 297 sessions without being chosen, and chosen in 61. That is a 17% 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.