Comet tracks a cargo ship and sets a follow-up

Sidney Hori describes a first week using Comet for browser tasks. One completed workflow concerns a cargo shipment to Brazil: the assistant finds the ship name in an email, uses an online vessel tracker to obtain the ship's location and estimated arrival, then creates a Google Calendar reminder to follow up.

The important handoff is the identifier. Email supplies the ship name that the next website needs, and the tracking result becomes a reason to schedule a follow-up. This is an agent moving between connected information and a browser-based research tool, then acting in a calendar, rather than merely explaining how someone could track a shipment.

The account gives no carrier name, exact arrival time, calendar screenshot or final delivery confirmation. An estimated arrival is therefore the result of the lookup, not proof that the cargo arrived. Hori's other first-week examples also include browser limitations, so the post should not be read as a reliability benchmark for every connected service. The reader's concrete starting brief can identify the relevant shipment email, ask for the vessel's current tracking result and state the desired follow-up timing. Checking which vessel and calendar were selected remains necessary when repeating the workflow.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: LinkedIn · Sidney Hori