# ChatGPT Agent was asked to turn a year of grocery purchases into a spreadsheet: it clicked correctly but ran out of browsing context and quit

ChatGPT Dots · Reddit · Nothing is disclosed. There are no amounts, savings or income figures; the annual purchase spreadsheet was never completed.

## Business summary

Reddit user u/mrbritchicago posted 'My quick notes on first day of using Agent' in r/OpenAI. (the post title only says 'Agent', posted in r/OpenAI in July 2025; this site files it under ChatGPT Dots for display.) First he had it put 200 companies from a Forbes link spread over five pages into a spreadsheet; that one was completed decently, though it stopped several times from context limits and confusion and had to be re-prompted (Deep Research had failed at the same task the day before). He then asked it to find LinkedIn links for every company in a new column, thought it had done well, and added an EDIT: on looking at the spreadsheet he found it had stopped halfway, leaving half the entries without a link. He also notes that the agent clicks PDF links but the tab it opens in its browser is blank, and that a multi-step website task involving moving documents into different 'stages' followed only the first part and completely ignored the second, despite his very explicit prompts. His deliberate experiment was to have the agent log into his grocery store account, look at all his 2025 purchases, dedupe them and put them into a spreadsheet. It did decently from a technical standpoint - clicking the right things and using the correct spreadsheet format - but gave up far before completing the task because it ran out of browser context. He says he has not found any task he could set and forget; every task needed babysitting because each one stopped halfway. He ends by asking others about the browsing context limit and PDF reading. There is no completed annual spreadsheet, no row count, no amounts and no savings or income figure. The collection site's summary says the task 'worked but wasn't set-and-forget'; the original says it gave up far before completing, and this page follows the original. The workflow, prompt, synthetic sample and the 'credentials stay with the owner' boundary are AgentFlow proposals, not the author's practice.

## Business value

The reusable design is to treat 'stops halfway' as the default, not the exception: small batches, a coverage report per batch, unfinished ranges marked explicitly, and a human check before anything is called done. The post's most expensive moment was the LinkedIn task - the author thought it was finished, then looked at the sheet and found half the rows had no link. Make the coverage report an output before worrying about automation. Nothing here was run; the batching, checkpoints and credential boundary are AgentFlow proposals, not what the author did.

## Workflow

Split the year into small batches instead of asking for everything at once. (AgentFlow's response to the browser-context failure.)

Keep account login and credentials with the owner; the assistant only receives an export. (AgentFlow's boundary; the post describes the agent logging in.)

Report row count and date coverage at the end of every batch before continuing. (AgentFlow's fix for the half-finished LinkedIn column.)

Fix the dedupe rule up front and list duplicates without silently deleting rows.

Record any stop, blank PDF tab or skipped stage as an explicit breakpoint and stop there - never backfill with guesses.

Only the owner checks totals and marks the final spreadsheet complete. (AgentFlow's boundary.)

## Preparation and limitations

The post does not say which grocery account, how many purchases 2025 contained, what the dedupe rule was, what browser context limit was hit, what the blank PDF tab contained, what the exact prompts were, what the agent cost, or whether any spreadsheet was ever finished. It gives no amounts, no time saved and no row totals. The 200 companies and five pages describe task size, not results. No reproduction was attempted; the sample here is synthetic.

## Starter prompt

````text
You are my purchase-history organiser. You may process only the export file I give you, batch by batch, deduplicate and draft a spreadsheet. You do not log in, hold credentials, enter passwords, submit or send anything, and you do not backfill data when a batch stops early.

[INPUT]
- Purchase export: [path], with at least date / item / amount / order id
- Batch split: [e.g. by month, or every 50 rows]
- Period: [start and end dates]
- Dedupe rule: [e.g. identical date + item + amount + order id counts as duplicate]
- Spreadsheet fields: [field names and order]
- Note: I log in and export the data myself; you only receive the export file.

[STEPS]
1. Report total rows, the dates covered and any missing fields. If fields are missing, stop here and say which step is affected.
2. Process one batch at a time. At the end of each batch report: rows read, dates covered, rows processed, rows unprocessed, and whether the batch finished. Wait for my confirmation before the next batch.
3. Within each batch, find duplicates under the fixed rule and output a duplicate list with original row numbers. Do not silently delete or merge rows.
4. Draft the spreadsheet, marking any unfinished or interrupted batch's range as 'incomplete' and stating which step it stopped at.
5. Produce a breakpoint table: batch / step stopped at / unfinished range / reason (context exhausted, blank page, missing fields) / what I need to do.
6. End with a check list: do draft totals match the export, which ranges to spot-check, who signs off - and state that no account was accessed and nothing was sent.

[OUTPUT]
1) read report; 2) per-batch coverage report; 3) duplicate list; 4) spreadsheet draft with incomplete ranges; 5) breakpoint table; 6) check list and no-send statement.

[NEEDS MY CONFIRMATION]
- Whether to continue after each batch: I decide.
- Whether duplicates are merged, and under which rule: I decide.
- Any account login, credential entry, submission or external send: I do it myself.

[IF MATERIAL IS MISSING OR A STEP FAILS]
Unreadable export, missing fields, a batch stopping midway, a PDF or page opening blank, row counts that do not reconcile: record it in the breakpoint table and stop at that batch. Never fill gaps with guesses, rounding or older data, and never mark a half-finished sheet as complete. An explicit incomplete range is better than a sheet that looks complete but is missing half its rows.
````

## Costs and pitfalls

The post does not say which grocery account, how many purchases 2025 contained, what the dedupe rule was, what browser context limit was hit, what the blank PDF tab contained, what the exact prompts were, what the agent cost, or whether any spreadsheet was ever finished. It gives no amounts, no time saved and no row totals. The 200 companies and five pages describe task size, not results. No reproduction was attempted; the sample here is synthetic.

## Source and attribution

mrbritchicago（Reddit 用户 u/mrbritchicago，原帖作者本人，自述记录使用 Agent 第一天的多项实测） (u/mrbritchicago)
https://www.reddit.com/r/OpenAI/comments/1m8hbzf/my_quick_notes_on_first_day_of_using_agent/
2025-07-24
Results come from the source author. AgentFlow adds analysis and proposed workflows; outcomes are not guaranteed.
