Dots hits repeated approvals on a shuttle booking
neom reports that Dots spotted a missing airport shuttle and filled its booking form, but kept requesting approval after repeated confirmations.
news.ycombinator.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Review my booked flight and hotel, identify any missing airport transfer, and prepare suitable shuttle details. Show the current booking state and request the specific confirmation required before submitting payment.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- neom
- Original account
- Read the source ↗
- Published
- 30 Sept 2026
- Source link checked
- 15 Oct 2026
- Reported result
- neom reports that Dots spotted a missing airport shuttle and filled its booking form, but kept requesting approval after repeated confirmations.
- Human involvement
- neom booked the flight and hotel, repeatedly confirmed the shuttle details and had to handle emailed authentication codes. A completed shuttle reservation is not established.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Ask Dots to plan the trip, then book the flight and hotel yourself.
- Have Dots identify the missing shuttle and revisit the booking website.
- Confirm the itinerary details and let Dots fill the form.
neom tried Dots for two hours while arranging a trip. The agent helped work out the travel plan, and neom booked the flight and hotel. Dots then noticed that the airport shuttle was missing, recalled the details already discussed and offered to handle that remaining booking.
The difficulty appeared at the approval boundary. After receiving permission, Dots returned to the website, checked the agreed details and asked for confirmation. neom confirmed again. The agent filled the booking form on its cloud computer, then returned with another request to book. The account describes this repeated loop without establishing that the shuttle reservation was completed.
The same trial exposed a separate authentication limit. Dots could use supplied account credentials, but would not retrieve and enter an emailed two-factor code even with inbox access. neom also tried broad permission rules for routine tasks and Slack replies. The permission checker rejected them as too broad.
This is a concrete account of partial execution and friction, rather than a completed autonomous itinerary. The user still made purchases and handled authentication. Useful planning and form entry did not eliminate the need to understand which approvals the service would accept.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Hacker News · neom
Frequently asked questions
Did Dots book all the travel?
No. The user booked the flight and hotel. The account describes a shuttle form and repeated approvals, without confirming a completed shuttle reservation.
Could it enter emailed two-factor codes?
The user says Dots would not retrieve and enter the codes, even though the agent could access the inbox.
Did broad permission rules remove the interruptions?
No. The permission checker rejected the examples described in the comment as too broad.
More details
Remaining steps
- Inspect repeated approval requests; the account does not confirm a finished shuttle booking.
About this account
Dots recalled a missing shuttle, revisited the provider website, checked the details and filled the booking form, then continued requesting approval.
Firsthand public account opened and read; author and original timestamp verified against the official Hacker News item API. Outcomes are author reports, not independently reproduced. Suggested prompt written by Agents In Use.
Credit: neom on Hacker News
Source published 30 Sept 2026
Source checked 15 Oct 2026
Tools and topics
Dots · Cloud browser · Email authentication
Travel planning · Booking approvals · Authentication
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.