Update fields on 400 ERP transactions in the browser
The author had Claude's Chrome extension edit 2 fields across about 400 ERP transactions; it was slow, asked for confirmation at each step and burned token limits, but ran in the background. Task: Suggested implementation: Use Claude in Chrome to update two fields across approximately 400 ERP transactions, a task typically requiring two hours of manual effort. The workflow involves configuring the extension with a software engineer's assistance and iteratively refining prompts to guide screenshot-based navigation. Human oversight is critical for verifying each step and managing prompt adjustments.; tools: Claude in Chrome. Human role: The original post does not say how a person stayed involved.; limitations: Prompt phrasing significantly altered the steps Claude took, necessitating extensive iteration. Screenshot-driven actions consumed tokens rapidly, and visibility into token usage was limited. The setup required technical assistance, and the system demanded confirmation at each step, preventing true background automation..
Tools
Published on Agent Work Atlas:
Overview
The author had Claude's Chrome extension edit 2 fields across about 400 ERP transactions; it was slow, asked for confirmation at each step and burned token limits, but ran in the background.
Workflow
Suggested implementation: Use Claude in Chrome to update two fields across approximately 400 ERP transactions, a task typically requiring two hours of manual effort. The workflow involves configuring the extension with a software engineer's assistance and iteratively refining prompts to guide screenshot-based navigation. Human oversight is critical for verifying each step and managing prompt adjustments.
Reported result
The process was extremely slow, with token limits exhausted in about half of the attempts, resulting in five-hour waits for refreshes. The author spent at least as much time and effort on this automated approach as on the manual process. No successful completion metrics are available, indicating the workflow failed to save time.
Human role
The original post does not say how a person stayed involved.
Limitations
Prompt phrasing significantly altered the steps Claude took, necessitating extensive iteration. Screenshot-driven actions consumed tokens rapidly, and visibility into token usage was limited. The setup required technical assistance, and the system demanded confirmation at each step, preventing true background automation.
Try it
Act as a business operations specialist. I need to test the feasibility of using Claude in Chrome to update [Field A] and [Field B] for [Number] ERP transactions. First, perform a dry run on a sample of 10 transactions using [Sample Transaction IDs]. Monitor token consumption and time per transaction. If the sample fails or exceeds [Max Time] minutes, stop and report the error. If successful, proceed to the next batch of 20. Require my explicit confirmation before processing any real data. Output a report comparing the automated time against the manual baseline of [Manual Time] minutes. Do not proceed if token limits are hit without a clear recovery plan.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.