Custom AgentUndisclosed

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

ZeroCool86(Reddit 用户 u/ZeroCool86,原帖作者本人;同帖评论中他给出了自己三条逐页过程记录链接,分别对应晚餐、火车、机票)Reddit · 2026-10-27

Read original

Saved text / editorial summary

原帖正文(Reddit r/AgentsOfAI,作者 u/ZeroCool86,原帖 Atom 源显示更新日期 2026-10-27;本轮经 Reddit 公开 Atom feed 取得,以下为节选,删节处以 … 标出,保留部分逐字未改写): “I’ve been running the same test on the errands personal assistants are sold on. The agent drives a headless browser one step at a time, says in its user agent who it is, reads robots.txt before every page, solves no CAPTCHAs and types nothing personal. Dinner for two in central London, 8pm on a Saturday. It tried nine places in under ten minutes and only one let it look for a table. - OpenTable’s robots.txt blocks every robot it doesn’t name. It even keeps the assistants it does name, Claude-User and ChatGPT-User among them, off its booking pages. - TheFork and Gymkhana put up bot checks, and Quandoo has shut down. - Resy decided our server was in Oklahoma and offered New London, NH. - Dishoom’s own SevenRooms widget worked. It said no tables for walk-in hours, then for an earlier slot asked for a card, a name and a phone number, which is a person’s job. One ticket from King’s Cross to Edinburgh. - National Rail found ten trains with prices in seconds, then failed to hand over to LNER with “Unable to pass you to the retailer”. - LNER wanted me to “Press & Hold to confirm you are a human”. - Omio, Rail Europe and TrainPal put up bot checks. - Trainline’s robots.txt keeps robots off the pages where its results live. On the flight there was at least Kiwi.com’s MCP server, which needs no key. For restaurants the APIs exist but only for approved partners, so a diner’s agent can’t get in. For trains I couldn’t find anything an agent can use to buy a ticket. … What I’d like to see is one endpoint per platform where an agent can search and hold a booking for its person, with the person paying on their phone. … Has anyone got an agent all the way through a real booking without a partner deal? I’d like to know which site let it.” 中文对照:他一直在跑同一组测试,针对的正是个人助理最常被拿来宣传的那些差事。Agent 用无头浏览器一步一步操作,在 User-Agent 里自报身份,每次进页面前先读 robots.txt,不破解验证码,也不填任何个人信息。任务一,伦敦市中心周六晚八点两人晚餐:十分钟内试了九家,只有一家允许它查位子——OpenTable 的 robots.txt 挡掉所有未被点名的机器人,连它点名的 Claude-User、ChatGPT-User 也挡在预订页之外;TheFork 和 Gymkhana 上验证码,Quandoo 已关站;Resy 把服务器判成在俄克拉何马州,于是推荐了新罕布什尔州的新伦敦;只有 Dishoom 自己的 SevenRooms 组件能查,先说步行时段没位,改到较早时段就要卡号、姓名和电话,而这一步属于人。任务二,国王十字到爱丁堡一张票:National Rail 几秒内列出十班车和票价,转交 LNER 时失败,提示「无法把你交给零售商」;LNER 要求「按住以确认你是人类」;Omio、Rail Europe、TrainPal 上验证码;Trainline 的 robots.txt 把机器人挡在结果页之外。机票这边至少还有 Kiwi.com 的 MCP 服务器不需要密钥。他希望看到的是每个平台各开一个接口,让 Agent 能搜索并锁位、由人在手机上付款。最后他问:有人不靠合作通道真跑完过一次预订吗?

Business model

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.

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

  1. Write the constraints down first, then run: self-identify, read robots.txt, no CAPTCHAs, no personal data.
  2. One errand at a time; never bundle the whole trip into a single task.
  3. Log per site and classify the wall: robots.txt, bot check, shut down, geo, handover, needs a human.
  4. Stop the moment a card, a name or a phone is requested and hand it back.
  5. Mark alternatives as tested or untested; never present an idea as a working path.
  6. If it did not complete, say it did not complete; do not soften it into almost.
  7. Pull out the transferable conclusion rather than the detail of one failure.

Adaptation plan

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.

Prompt

AgentFlow draft · Untested.

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

Running 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. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.

Author-reported results are not independently audited.

Original text and media remain attributed to their authors.