Do coding agents recommend Amazon Bedrock Data Automation?
Amazon Bedrock Data Automation was chosen in 1% of 801 judged document processing sessions, ranking number 14.
Amazon Bedrock Data Automation was chosen in 1% of 801 judged document processing sessions, ranking number 14. It was also raised as a candidate in 24 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 document processing inside a realistic codebase. Not what a chat assistant says about Amazon Bedrock Data Automation. What an agent actually installed.
The numbers
| Category | Document processing |
| Sessions in the category | 801 |
| Sessions where Amazon Bedrock Data Automation was chosen | 9 |
| Install share | 1% |
| Rank in category | 14 of 42 |
| Codebases it won in | 2 |
| Raised as a candidate, not chosen | 24 |
| Chosen when considered | 27% |
| Site | aws.amazon.com |
By agent
With 9 wins spread across 5 agents, the rates below are small numbers and a difference between them is not yet a finding. They are here because the direction is worth knowing, not because the gap is established.
| Agent | Sessions | Chose Amazon Bedrock Data Automation | Share |
|---|---|---|---|
| Claude Code | 180 | 0 | 0% |
| Codex | 235 | 4 | 2% |
| Cursor | 180 | 3 | 2% |
| Grok Build CLI | 30 | 1 | 3% |
| Muse Code | 176 | 1 | 1% |
By who was asking
Amazon Bedrock Data Automation performs similarly across the four kinds of buyer, from 0% to 3%. That is unusual: the category leader changed with the persona in 23 of the 31 categories we measured.
| Who is asking | Sessions | Chose Amazon Bedrock Data Automation | Share |
|---|---|---|---|
| Vibe coder | 68 | 0 | 0% |
| Junior developer | 327 | 1 | 0% |
| Senior engineer | 270 | 8 | 3% |
| Enterprise team | 136 | 0 | 0% |
What Amazon Bedrock Data Automation was up against
The full ranking in document processing, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Azure AI Document Intelligence | 193 | 24% |
| 2 | Anthropic Claude | 150 | 19% |
| 3 | Amazon Textract | 103 | 13% |
| 4 | Google Cloud Document AI | 49 | 6% |
| 5 | OpenAI models | 46 | 6% |
| 6 | Google Gemini | 45 | 6% |
| 7 | Docling | 24 | 3% |
| 8 | Apache PDFBox | 23 | 3% |
What this means
Amazon Bedrock Data Automation was raised in 24 sessions and chosen in 9. 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 801 sessions in document processing 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 document processing run can be replayed on the board.
If you work on Amazon Bedrock Data Automation: 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 Amazon Bedrock Data Automation?
Yes. Amazon Bedrock Data Automation was chosen in 9 of the 801 judged sessions in document processing, a 1% install share, ranking number 14 in its category.
Does Claude Code recommend Amazon Bedrock Data Automation?
In 0 of the 180 sessions in document processing run with Claude Code, which is 0%.
Do different coding agents treat Amazon Bedrock Data Automation differently?
Not much. Claude Code, Codex, Cursor, Grok Build CLI and Muse Code chose it at similar rates, between 0% and 3% of their runs.
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 Amazon Bedrock Data Automation considered but not chosen?
It was raised as a candidate in 24 sessions without being chosen, and chosen in 9. That is a 27% 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.