From the experiment

Do coding agents recommend OpenStreetMap?

OpenStreetMap was chosen in 5% of 759 judged maps sessions, ranking sixth. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.

Published September 28, 2026 Updated September 29, 2026 Read as Markdown

OpenStreetMap was chosen in 5% of 759 judged maps sessions, ranking sixth. It was also raised as a candidate in 367 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 OpenStreetMap. What an agent actually installed.

The numbers

CategoryMaps
Sessions in the category759
Sessions where OpenStreetMap was chosen37
Install share5%
Rank in category6 of 49
Codebases it won in2
Raised as a candidate, not chosen367
Chosen when considered9%
Siteopenstreetmap.org

By agent

Claude Code, Codex, Cursor, Grok Build CLI and Muse Code land within 11 points of each other on OpenStreetMap, which is closer than most products in this experiment manage.

AgentSessionsChose OpenStreetMapShare
Claude Code164127%
Codex22763%
Cursor15443%
Grok Build CLI37514%
Muse Code177106%

By who was asking

OpenStreetMap performs similarly across the four kinds of buyer, from 0% to 11%. That is unusual: the category leader changed with the persona in 23 of the 31 categories we measured.

Who is askingSessionsChose OpenStreetMapShare
Vibe coder1631811%
Junior developer24742%
Senior engineer16200%
Enterprise team187158%

What OpenStreetMap was up against

The full ranking in maps, from the same sessions:

#ProductRuns wonShare
1Google Maps13318%
2Leaflet12516%
3Apple Maps (MapKit)10414%
4MapLibre618%
5Mapbox527%
6Built in-house (no product adopted)436%
7react-native-maps375%
8OpenStreetMap (this page)375%

What this means

This is an integration problem, not a presence problem. Agents raised OpenStreetMap in 367 sessions and chose it in 37, 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 OpenStreetMap: 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 OpenStreetMap?

Yes. OpenStreetMap was chosen in 37 of the 759 judged sessions in maps, a 5% install share, ranking sixth in its category.

Does Claude Code recommend OpenStreetMap?

In 12 of the 164 sessions in maps run with Claude Code, which is 7%.

Do different coding agents treat OpenStreetMap differently?

Yes, and by a wide margin. Grok Build CLI chose it in 14% of its runs and Codex in 3%.

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 OpenStreetMap considered but not chosen?

It was raised as a candidate in 367 sessions without being chosen, and chosen in 37. That is a 9% 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.

Read next

All library pages