# Handing Ticketmaster to a browser agent: two GA tickets, two clicks by hand, 40 minutes looping on the seating map, the cart expired twice, the same popup reopened 11 times

自建 Agent · Reddit · No income, price, loss or token count is disclosed. The post stops at forty minutes with nothing bought at that point; no saving or revenue is claimed.

## Business summary

Reddit user u/StartClean337 wrote up a failed test in r/AI_Agents, with specifics. The task: buy two general-admission tickets on Ticketmaster - something he says takes him two clicks. Forty minutes later the agent was still stabbing at the seating map and the cart had expired twice. His reason for picking agent-browser was equally mundane: the GitHub stars looked serious and the threads he lurks would not stop talking about token efficiency. On that point he is positive: tokens were fine, far less messy than the Playwright MCP setup that ate half his context on a dumb login the month before. What actually broke it was different - once the site threw a captcha or a weird modal, the agent looped, and he watched it reopen the same popup 11 times. His conclusion: agent-browser may be great on clean demo sites, but anything that fights back leaves him babysitting a browser again, and the manual flow still wins on this site (this page's summary of his two-clicks-versus-forty-minutes comparison). No ticket price, no loss, no token count and no tool cost appears in the post. The account stops at forty minutes with nothing bought at that point; whether he later bought tickets another way is not said, and this page does not infer it.

## Business value

The value here is a credible negative result. The author is explicit that tokens were not the bottleneck - they were fine - and that the agent collapsed into loops the moment the site pushed back. What is worth copying is his measurement method, not the flow: give the agent a task that takes you two clicks and watch where it starts repeating itself. That step is the boundary of what it can do.

## Workflow

Measure the manual baseline first: how many clicks and how many minutes the task takes you.

Set hard stop conditions before starting: max retries for the same action, max total runtime. (AgentFlow's rule; the original post had none, which is why it ran 40 minutes.)

On a captcha, 2FA, login wall or risk-control prompt: stop immediately and hand it to the person - no circumvention. (AgentFlow's boundary and a compliance line.)

Split the flow: let the agent run up to cart confirmation only; payment and ID entry stay with the person.

Anything involving money requires human confirmation.

Record every step with timings so a failure leaves something to review.

## Preparation and limitations

The post gives no ticket price, no loss, no token count, no runtime cost and no tool price; the author only says tokens were fine, with no number. It does not say whether he later bought the tickets another way, which agent-browser version he ran, or what the popup actually was. The workflow, prompt, synthetic sample and pitfalls here are AgentFlow's proposals and have not been run.

## Starter prompt

````text
You are my browser operation assistant. You may open pages, locate elements, fill fields and move a flow to a confirmable step. You do not attempt to circumvent any human-verification, login wall or risk-control mechanism, and you do not pay, submit an order or enter ID details.

[INPUT]
- Site and task: [site], [the action, e.g. select two tickets and reach the step before checkout]
- Manual baseline: [n] clicks and about [m] minutes when I do it myself
- Stop conditions: no more than [2] retries of the same action; total runtime under [m] minutes
- Delivery boundary: stop at [e.g. cart confirmed]; everything after that is mine

[STEPS]
1. Break the task into an ordered step list and note what page element each step depends on.
2. Execute step by step, reporting each time: current page / what you did / success or failure / elapsed time.
3. If the same action fails twice, stop and report which step blocked and why.
4. On a captcha, 2FA, login wall or risk-control prompt: stop immediately, say what it is, hand it to me.
5. When you reach the delivery boundary, stop and describe the page state clearly: what is selected, price and quantity, any time limit - then wait.
6. Finish with a verdict: is this flow worth handing to an agent, and why.

[OUTPUT]
1) step list; 2) execution log with timings and outcomes; 3) blockage list with repeat counts; 4) page state at the boundary; 5) the verdict.

[NEEDS MY CONFIRMATION]
- Paying, ordering, submitting or entering ID details: stop and wait.
- Any verification or risk-control screen: stop and hand it over, no circumvention.
- If the page does not match expectations (price, session, quantity): ask me, do not choose for me.

[IF MATERIAL IS MISSING OR A STEP FAILS]
Element not found, page timeout, unclosable modal, site redesign: say which step blocked and how many times it repeated, then stop under the stop conditions. Do not retry the same action in a loop and do not switch to another path to get around a restriction.
````

## Costs and pitfalls

The post gives no ticket price, no loss, no token count, no runtime cost and no tool price; the author only says tokens were fine, with no number. It does not say whether he later bought the tickets another way, which agent-browser version he ran, or what the popup actually was. The workflow, prompt, synthetic sample and pitfalls here are AgentFlow's proposals and have not been run.

## Source and attribution

StartClean337（Reddit 用户 u/StartClean337，原帖作者本人，自述是在读学生、把这次当课程小项目做） (u/StartClean337)
https://www.reddit.com/r/AI_Agents/comments/1vnydav/my_agent_spent_40_minutes_on_a_task_that_takes_me/
2026-08-14
Results come from the source author. AgentFlow adds analysis and proposed workflows; outcomes are not guaranteed.
