I run OpenGeocoding. Originally published on the OpenGeocoding blog . Cross-post formatting was prepared with AI assistance.
A coding agent can write a fix for a geocoding bug in minutes. The hard part is knowing whether the fix is right, and whether it quietly broke something in another country. That is a question for the harness the agent works in, not for the agent. This post describes the harness around the OpenGeocoding engine: what checks every change, why the world index had to rebuild quickly for any of it to work, and the part that still isn’t stable, which is the speed gate.
The engine’s public repository merged 281 pull requests between 12 and 27 October 2026, and many of them were written by a coding agent. At that pace, I can’t judge every change by reading it. I need the checks to tell me what the change did to the whole world.
Why a geocoder needs this more than most code
Address matching is a long list of rules that interact.…