Claude fills a web tax organizer through JSON
Alex Willen used Claude in Chrome to extract a tax organizer’s fields, Claude Code to populate JSON from records and Chrome to enter reviewed pages, with repeated human batching.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Extract this organizer’s fields into small structured batches, populate only values supported by my approved records and flag missing data. Return the batches for reviewed entry and reconcile the displayed fields with the source records.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- Alex Willen
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- Willen reports correct organizer entry after human batching and review, while separate tax analysis in the same account exposed missed checks and errors.
- Human involvement
- Willen manually copied JSON, divided pages, supplied records and thoroughly reviewed the completed organizer before relying on it.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Extract the embedded organizer fields with Claude in Chrome.
- Transfer JSON to Claude Code and populate it from approved records.
- Request missing-information flags and split work after truncation and limits.
Alex Willen's accountant supplied a tax organizer inside a web application, with no downloadable fillable copy. Willen used Claude in Chrome to extract a JSON representation of the fields, then passed that structure to Claude Code, which already held context from his bookkeeping and tax documents.
The extraction did not finish in one pass. Output stopped partway through page seven, and a later batch hit a usage limit. Willen split the remaining work into small page groups, copied the JSON between the products and asked Claude Code to identify missing information rather than silently guess.
He then returned populated JSON to Claude in Chrome three pages at a time. Willen reports that a thorough review found the entered organizer correct. The workflow depended on human transfer, batching and final inspection rather than seamless agent-to-agent delegation.
The wider article also describes tax-review failures. Claude initially said a prior return looked fine without comparing every document, and a separate reconstruction experiment produced tax errors. Those findings limit any inference from successful form entry to tax correctness. The useful artifact here is a completed organizer assembled through a structured handoff, with the accountant still responsible for the return and the owner checking the web fields.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Blog · Alex Willen
Frequently asked questions
Why was JSON used?
The organizer was embedded in the accountant’s application, so JSON carried field structure to Claude Code and completed values back to Chrome.
What prevented a single uninterrupted run?
Extraction truncated around page seven and later hit a usage limit; the owner split the work into small batches.
Does correct entry establish correct tax advice?
No. The article separately documents tax reasoning and reconstruction errors despite the successful organizer workflow.
More details
Remaining steps
- Return small JSON page batches to Chrome and inspect every entered field.
About this account
Claude in Chrome extracts and enters organizer fields; Claude Code fills the JSON and flags missing values.
Firsthand primary account opened and read; original publication date checked in primary metadata or visible timestamp. Outcomes are author-reported, not independently reproduced. Suggested prompt written by Agents In Use. Human transfers and batching were essential; successful organizer entry is not an audit of tax correctness.
Credit: Alex Willen
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude in Chrome · Claude Code · JSON files · Accountant web organizer
Money, bills · Reported deployment
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.