ChatGPT agent attempts an OpenTable reservation
Ben Patterson watched ChatGPT agent navigate OpenTable for a party of three, correct a party-size error and stop for diner details before final confirmation.
pcworld.com
Original prompt
Shared by the source author. See source notes for context.
Book me a table at Rosa Mexicano in Turtle Bay NYC, party of three, tonight, around 6:30 pm.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- Ben Patterson
- Original account
- Read the source ↗
- Published
- 28 Apr 2026
- Source link checked
- 15 Oct 2026
- Reported result
- The agent reportedly held a table after correcting the party size, then stopped for human diner details; final booking is unverified.
- Human involvement
- Patterson watched the run and retained the diner-details handoff; a final confirmation is not reported.
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
- Specify the venue, party size and desired dinner time in ChatGPT agent.
- Let the agent navigate OpenTable and correct the party-size selection.
- Take over when personal diner details are needed before finalizing.
Ben Patterson compared a Claude Resy connector with ChatGPT agent for dinner reservations. The connector displayed availability but sent him to Resy to finish. He then used ChatGPT's browser agent to attempt a reservation at Rosa Mexicano in Turtle Bay, New York, for three people around 6:30 that evening.
The agent opened OpenTable and worked through its interface. Patterson observed slow clicking and scrolling, including difficulty with the party-size dropdown. The agent noticed it had selected two people and reopened the control to choose three.
After roughly five minutes, it reported that a table was being held and asked Patterson to take over to enter the diner details. The source ends at that handoff. It does not report a confirmed reservation from this agent run.
The failure to finish is the useful outcome. Patterson had provided a specific venue, time and party size, yet ordinary booking controls still required correction and human completion. The article distinguishes browsing automation from the more limited connector path. Its observations support one attempted reservation and a recoverable parameter error, without implying that all OpenTable sessions fail or that the model completed the transaction.
Prompt
Original prompt
Source: Blog · Ben Patterson
Frequently asked questions
Was the reservation confirmed?
The account reports a held table and takeover request, not a final confirmed reservation.
What did the agent get wrong?
It initially selected two diners instead of the requested three, then noticed and corrected the dropdown.
Was this the same as the Resy connector test?
No. Patterson separately tried a connector that displayed slots and redirected him to Resy; this case follows the browser agent.
More details
About this account
The agent navigates OpenTable, corrects party size and reaches the personal-details handoff.
Firsthand primary account opened and read; original publication date checked in primary metadata or visible timestamp. Outcomes are author-reported, not independently reproduced. Original linked from secondary discovery article. Final reservation not confirmed. Original prompt excerpt reproduced exactly from the source; excerpt only, not the complete prompt.
Credit: Ben Patterson
Source published 28 Apr 2026
Source checked 15 Oct 2026
Tools and topics
ChatGPT agent browser · OpenTable
Travel · Reported deployment
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.