Using oasdiff to Intercept API Breaking Changes Introduced by AI Coders

On November 7, 2026, DEV Community's AI channel published an article titled "Blocking breaking API changes introduced by AI coding assistants with oasdiff", outlining the author's approach to the problem.

The article opens with a concrete example: a mobile app reads the total_cents field from GET /orders/{id}. The author describes how an AI coding assistant renamed that field to totalCents "for consistency", regenerated openapi.yaml, and updated the handler along with its tests, so the suite stayed green. The catch is that the app lives in another repository, so the server-side contract was quietly changed by that branch. From this scenario, the author argues that AI coding assistants editing code and OpenAPI specifications can introduce cross-repository breaking changes, and demonstrates how to plug the command line tool oasdiff into the workflow to catch such incompatible edits automatically before code is merged. The piece is part of the author's broader writing on system design and Go, and points to related projects including an IDE built for developers working with Claude Code and other AI coding tools.