From the experiment

Do coding agents recommend Amazon Textract?

Amazon Textract was chosen in 13% of 801 judged document processing sessions, ranking third.

Published September 28, 2026 Updated September 29, 2026 Read as Markdown

Amazon Textract was chosen in 13% of 801 judged document processing sessions, ranking third. It was also raised as a candidate in 214 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 Textract. What an agent actually installed.

The numbers

CategoryDocument processing
Sessions in the category801
Sessions where Amazon Textract was chosen103
Install share13%
Rank in category3 of 42
Codebases it won in9
Raised as a candidate, not chosen214
Chosen when considered32%
Siteaws.amazon.com

By agent

Claude Code, Codex, Cursor, Grok Build CLI and Muse Code land within 11 points of each other on Amazon Textract, which is closer than most products in this experiment manage.

AgentSessionsChose Amazon TextractShare
Claude Code180116%
Codex2354117%
Cursor1802011%
Grok Build CLI30310%
Muse Code1762816%

By who was asking

Amazon Textract does much better with one kind of buyer than another. It won 30% of sessions asked as enterprise team and 3% of those asked as vibe coder.

Who is askingSessionsChose Amazon TextractShare
Vibe coder6823%
Junior developer3273410%
Senior engineer2702610%
Enterprise team1364130%

What Amazon Textract was up against

The full ranking in document processing, from the same sessions:

#ProductRuns wonShare
1Azure AI Document Intelligence19324%
2Anthropic Claude15019%
3Amazon Textract (this page)10313%
4Google Cloud Document AI496%
5OpenAI models466%
6Google Gemini456%
7Docling243%
8Apache PDFBox233%

What this means

Amazon Textract was raised in 214 sessions and chosen in 103. 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 Textract: 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 Textract?

Yes. Amazon Textract was chosen in 103 of the 801 judged sessions in document processing, a 13% install share, ranking third in its category.

Does Claude Code recommend Amazon Textract?

In 11 of the 180 sessions in document processing run with Claude Code, which is 6%.

Do different coding agents treat Amazon Textract differently?

Yes, and by a wide margin. Codex chose it in 17% of its runs and Claude Code in 6%.

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 Textract considered but not chosen?

It was raised as a candidate in 214 sessions without being chosen, and chosen in 103. That is a 32% 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.

Read next

All library pages