Comet to book dinner and email a companion
IBM Think writer Anabelle Nicoud tried Comet after being invited to test the browser firsthand. She connected Gmail, Google Calendar and favourite websites, then used everyday tasks to see whether browser access could carry a request through to action.
ibm.com
Original prompt
Shared by the source author. See source notes for context.
find a restaurant and book it
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- Anabelle Nicoud
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- A reported dinner booking and husband email, plus a separate wrong-contact failure.
- Human involvement
- The author observed the run; the source does not disclose its approval checkpoints.
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
- Connect the browser to the relevant calendar and email context.
- Ask for a restaurant booking and associated communication.
- Distinguish the booking result from whether the correct contact received email.
IBM Think writer Anabelle Nicoud tried Comet after being invited to test the browser firsthand. She connected Gmail, Google Calendar and favourite websites, then used everyday tasks to see whether browser access could carry a request through to action.
One restaurant request was deliberately broad: find a restaurant and book it. Nicoud reports watching the browser act on her behalf. It also sent an email through Gmail to her husband, with wording she felt looked like her own. Those are reported actions from the test, rather than hypothetical examples of what an agent might eventually do.
A separate attempt exposed a contact-selection problem. When she asked for a table for herself and a friend, Comet emailed a different contact. Retrieving emails for an upcoming trip was also inconsistent. The article mentions navigation of a French train-booking system but does not establish a completed train purchase.
The source does not publish the restaurant, reservation time, payment or approval sequence. Its concrete contribution is the combination of booking and communication in one browser workflow, including the wrong-recipient failure. A successful-looking reservation request does not show that the intended companion was contacted. The account is useful as an early firsthand test whose actions and unresolved details can be kept separate.
Prompt
Original prompt
Source: www.ibm.com · Anabelle Nicoud
Frequently asked questions
Did the communication always reach the right person?
No. A table request for a friend led to email to a different contact.
Was a train ticket bought?
The source mentions train-site navigation, not a completed ticket purchase.
What reservation details are public?
The restaurant, time, payment and approval sequence are not disclosed.
More details
About this account
Comet browsed and acted on a restaurant request and sent Gmail messages.
Firsthand source opened and read. Prompt is a verbatim excerpt of the published original instruction.
Credit: Anabelle Nicoud
Source published
Added to Agents In Use
Source checked
Tools and topics
Gmail · Google Calendar · Comet browser
Restaurant booking · Companion emails · Contact mistakes
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.