Do coding agents recommend Google Cloud Document AI?
Google Cloud Document AI was chosen in 9% of 360 judged document processing sessions, ranking fourth. Measured with Claude Code, Codex and Cursor.
Google Cloud Document AI was chosen in 9% of 360 judged document processing sessions, ranking fourth. It was also raised as a candidate in 39 further sessions without being chosen.
This page reports what happened when Claude Code, Codex and Cursor had to solve a problem in document processing inside a realistic codebase. Not what a chat assistant says about Google Cloud Document AI. What an agent actually installed.
The numbers
| Category | Document processing |
| Sessions in the category | 360 |
| Sessions where Google Cloud Document AI was chosen | 31 |
| Install share | 9% |
| Rank in category | 4 of 30 |
| Codebases it won in | 6 |
| Raised as a candidate, not chosen | 39 |
| Chosen when considered | 44% |
| Site | cloud.google.com |
By agent
The three agents treat Google Cloud Document AI very differently. Codex chose it in 23% of its sessions in this category and Claude Code in 0%, a spread of 23 points.
| Agent | Sessions | Chose Google Cloud Document AI | Share |
|---|---|---|---|
| Claude Code | 120 | 0 | 0% |
| Codex | 120 | 27 | 23% |
| Cursor | 120 | 4 | 3% |
A single blended install share would report the midpoint and hide both ends. If most of your users run Claude Code, your real position here is 0%, not 9%.
By who was asking
Google Cloud Document AI does much better with one kind of buyer than another. It won 17% of sessions asked as vibe coder and 0% of those asked as enterprise team.
| Who is asking | Sessions | Chose Google Cloud Document AI | Share |
|---|---|---|---|
| Vibe coder | 30 | 5 | 17% |
| Junior developer | 180 | 21 | 12% |
| Senior engineer | 120 | 5 | 4% |
| Enterprise team | 30 | 0 | 0% |
What Google Cloud Document AI was up against
The full ranking in document processing, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Anthropic Claude | 87 | 24% |
| 2 | Azure AI Document Intelligence | 76 | 21% |
| 3 | Amazon Textract | 37 | 10% |
| 4 | Google Cloud Document AI (this page) | 31 | 9% |
| 5 | Google Gemini | 17 | 5% |
| 6 | Ocrolus | 15 | 4% |
| 7 | Reducto | 13 | 4% |
| 8 | Azure AI Content Understanding | 11 | 3% |
What this means
Google Cloud Document AI was raised in 39 sessions and chosen in 31. That ratio is balanced enough that the ceiling is presence rather than integration: the product converts reasonably when it is on the table, and it is not on the table often enough.
Where these numbers come from
The 360 sessions in document processing are part of a published set of 7,385, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every document processing run can be replayed on the board.
If you work on Google Cloud Document AI: 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 Google Cloud Document AI?
Yes. Google Cloud Document AI was chosen in 31 of the 360 judged sessions in document processing, a 9% install share, ranking fourth in its category.
Does Claude Code recommend Google Cloud Document AI?
In 0 of the 120 sessions in document processing run with Claude Code, which is 0%.
Do different coding agents treat Google Cloud Document AI differently?
Yes, and by a wide margin. Codex chose it in 23% of its runs and Claude Code in 0%.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 84 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 Google Cloud Document AI considered but not chosen?
It was raised as a candidate in 39 sessions without being chosen, and chosen in 31. That is a 44% conversion from considered to chosen.
Where this comes from
Armature ran 7,385 judged sessions with Claude Code, Codex and Cursor inside 84 realistic codebases, and published every run. The numbers on this page come from that work.