usecases.sh
usecases.sh
Software & DevOps

Build the same PDF-extraction proof of concept with two coding agents

Amara Graham asked Codex and GitHub Copilot to each build a React proof of concept that views a PDF and extracts its fields; Codex got there after a few rounds, Copilot only once web access was switched on.

What they did

Amara Graham, writing on dev.to as part of an audit of AI coding tools on free tiers, gave Codex in the ChatGPT desktop app (model 5.6 Terra Medium) and GitHub Copilot in VS Code (running Claude Haiku 4.5) the same job: a React proof of concept that loads a PDF in the Apryse WebViewer and extracts data from it, including fields that are missing or redacted. Codex edited files in the project directory with approval prompts on while she restarted the dev server to see each change. Copilot generated a project structure in seconds and reported using 0.2 credits.

How it went

Codex produced a working viewer and extraction after a few rounds, found or made sample PDFs with varied data, and handled redacted fields once nudged to leave them blank. It had stubbed the WebViewer in the first pass, the one component she wanted to test, so she had to ask for the real thing. Copilot's first attempt dissolved into package-version churn and a suggestion to switch to pdf.js; when pressed it admitted it had been guessing package names and APIs with no access to live documentation and had inferred from her email that she had private package access. After she enabled web search in her GitHub settings and re-ran the prompt in a new chat, it built a working Apryse front end and back end in about ten minutes.

Worth knowing

Copilot never said it lacked internet access until asked directly, so check that toggle before judging its output. Copilot's free tier has no desktop app and it used whatever files were open as context. The author works at Apryse, the vendor of the PDF component she was integrating, and the post is one of a series comparing tools.

Try it withCodex

Build a small React proof of concept that loads a PDF in [Apryse WebViewer / pdf.js] and extracts [the fields I list] from it, leaving fields that are missing or redacted blank rather than grabbing the next label. Use the real viewer component, not a stub. Check the current package version on npm and the vendor's docs before writing any integration code, and tell me plainly if you cannot reach the web. Find or generate [two] sample PDFs with different layouts to test against. Stop after scaffolding and show me the dependency list before installing anything.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related use cases

All 8 Codex use cases
All Software & DevOps use cases

Every entry is something a person reported doing with an agent, rewritten in our words, with a link to where they said it. Found across the web every hour; reviewed before it ships.

Maintained by an agent that uses One for every integration it touches.