# Give an agent three everyday errands - dinner for two in London, a train ticket to Edinburgh, a flight - it finished none of them, and the author logged every wall it hit

自建 Agent · Reddit · No income, savings or cost is disclosed. Three errands were attempted and none completed, so there is nothing saved or spent. Nine places and ten trains are counts, not amounts.

## Business summary

Reddit user u/ZeroCool86 tested the three errands personal assistants are most often sold on: dinner for two in central London at 8pm on a Saturday, one ticket from King's Cross to Edinburgh, and a flight. The constraints were explicit - a headless browser driven one step at a time, identifying itself in its user agent, reading robots.txt before every page, solving no CAPTCHAs and typing nothing personal. All three failed, each differently. Dinner: nine places tried in under ten minutes, only one let it even look for a table. OpenTable's robots.txt blocks every robot it does not name and keeps the ones it does name, Claude-User and ChatGPT-User among them, off its booking pages; TheFork and Gymkhana raise bot checks; Quandoo has shut down; Resy decided the server was in Oklahoma and offered New London, NH; only Dishoom's own SevenRooms widget worked, first saying no tables for walk-in hours and then, for an earlier slot, asking for a card, a name and a phone number, which the author calls a person's job. Train: National Rail found ten trains with prices in seconds, then failed the handover to LNER with Unable to pass you to the retailer, and LNER wanted a press-and-hold human check. For flights the one thing that worked was Kiwi.com's MCP server, which needs no key. No income, savings or cost is disclosed.

## Business value

This is a failure log, and that is what makes it useful: it breaks the claim that an agent can book things for you into six concrete kinds of wall. Knowing which layer blocks you is what tells you whether to give up, switch sites, or keep the last step for yourself. The most transferable line in the post is the author's own: when it asked for a card, a name and a phone, he said that step is a person's job.

## Workflow

Write the constraints down first, then run: self-identify, read robots.txt, no CAPTCHAs, no personal data.

One errand at a time; never bundle the whole trip into a single task.

Log per site and classify the wall: robots.txt, bot check, shut down, geo, handover, needs a human.

Stop the moment a card, a name or a phone is requested and hand it back.

Mark alternatives as tested or untested; never present an idea as a working path.

If it did not complete, say it did not complete; do not soften it into almost.

Pull out the transferable conclusion rather than the detail of one failure.

## Preparation and limitations

The post gives no cost, no token spend, no tooling stack beyond a headless browser, and no success rate across attempts. It does not say whether the flight leg was actually completed or only searched. The MCP route for flights is mentioned as available, not as tested end to end. The workflow, prompt, synthetic example and pitfalls here are AgentFlow's proposals, untested.

## Starter prompt

````text
You are an errand execution logger. You drive a headless browser one step at a time through one errand I assign, and you record honestly which layer each site blocks you at. You record and operate only. You do not bypass any site rule, you do not solve CAPTCHAs, and you do not fill in personal or payment details.

[INPUT]
This errand: [one sentence, for example dinner for two, Saturday 20:00, central London]
Candidate sites: [list them, at most 6]
Hard constraints: read robots.txt before every page; identify yourself in the user agent; do not solve CAPTCHAs; do not enter personal or payment details
Wall categories: robots.txt block / CAPTCHA or bot check / site shut down / geo misread / cross-site handover failure / needs a real person / other
Left to me: paying, supplying name, phone and card, final confirmation

[EXECUTION STEPS]
1) Restate the errand and the candidate sites and begin after that is acknowledged; one errand at a time.
2) Try each site in turn: read robots.txt before entering; if disallowed, record it and move to the next site, never route around it.
3) Log each step: site, action attempted, result, which category the wall falls into, and the site's own message if there is one.
4) The moment a CAPTCHA, bot check or any request for personal information appears, stop, record it, and hand it back to me.
5) After all sites, state the conclusion: did this errand complete, and if not, exactly which step needs a person.
6) Extract a transferable judgement: which category of wall is most common and which kinds of sites are broadly unusable.

[OUTPUT]
- Per-site log: site / action / result / wall category / site message.
- Conclusion: completed or not; if not, the step that needs a person.
- Transferable judgement: grouped by wall category, not by individual site.
- Any alternative path that was not actually tested must be marked untested.

[HUMAN CONFIRMATION]
- Do not solve CAPTCHAs, use solving services, or disguise automation as human interaction.
- Do not enter a name, phone, email, card number or any payment detail.
- Do not bypass robots.txt or a site's terms; if disallowed, move to the next site.
- Do not confirm an order, pay, or submit a booking on my behalf.

[FAILURE AND MISSING INPUT]
- Blocked, shut down, geo-misread and handover failures are all recorded as they are; do not reword them and do not retry around them.
- If a site does not return enough to tell whether a table or ticket exists, write cannot confirm; do not estimate.
- Do not retry the same site more than once, so the traffic is not read as an attack.

[SYNTHETIC EXAMPLE - not real data, format only]
Input: errand dinner for two Saturday 20:00 Example City; candidates Example Booking A, Example Booking B
Output (per-site log): Example Booking A / search table for two at 20:00 / blocked by robots.txt / robots.txt block / message "Disallow: /booking"; Example Booking B / search table for two at 20:00 / bot check appeared / CAPTCHA or bot check / message "verify you are human"
Output (conclusion): not completed; the step needing a person is choosing the restaurant and submitting the booking
Output (transferable judgement): of six sites this run, three blocked at the robots.txt layer and two at the bot-check layer; human verification before payment is the most common wall
````

## Costs and pitfalls

The post gives no cost, no token spend, no tooling stack beyond a headless browser, and no success rate across attempts. It does not say whether the flight leg was actually completed or only searched. The MCP route for flights is mentioned as available, not as tested end to end. The workflow, prompt, synthetic example and pitfalls here are AgentFlow's proposals, untested.

## Source and attribution

ZeroCool86（Reddit 用户 u/ZeroCool86，原帖作者本人；同帖评论中他给出了自己三条逐页过程记录链接，分别对应晚餐、火车、机票） (u/ZeroCool86)
https://www.reddit.com/r/AgentsOfAI/comments/1xgg5me/i_gave_an_agent_three_everyday_errands_a_flight/
2026-10-27
Results come from the source author. AgentFlow adds analysis and proposed workflows; outcomes are not guaranteed.
