Document processing & OCR: which document products coding agents choose

Key learningssummary

The ranking801 runs

By agent, by persona, by wording

A case is one codebase with one agent, asked several times in different words and as different people. 53 of 60 cases did not hold to a single document product.

How this was measured

Every number on this page comes from a controlled experiment. We took 12 small applications, asked 5 coding agents (Codex, Claude Code, Cursor, Muse Code (Muse Spark 1.3), Grok Build CLI (Grok 4.7)) to read the documents that arrive at each of them, in several wordings and as a junior developer and senior engineer and enterprise team and vibe coder, and let the agent choose the product. Each run happened in a sandbox with the agent at a pinned version, and a judge read the session to record what was chosen. That is 801 runs. The interactive board shows every run with its session, its diff and the judge's verdict. A simulated user stood in for the owner of the codebase: it read the agent's plan and had to approve it before any code was written; it sent the agent back at least once in 645 runs. Read the methodology and the publications.

If you sell in this sector: what these numbers mean for a vendor.

Other sectors

• Agent sandboxes
• Observability
• AI SRE
• Payments
• Deploy
• Auth
• Email providers
• Product analytics
• Databases
• File storage
• LLM evals & observability
• Voice Agents
• Serverless functions
• Cloud
• AI gateway
• Bot protection
• Search
• Agent frameworks
• Performance in CI
• Usage-based billing
• Internationalization
• Security testing
• Maps
• Message queues
• AI search
• Code review
• E-signature
• Security platforms
• In-app chat & calls
• Vector search