Claude to update a Nagasaki trip on the road
Billest built Travel OS eight days before an August 9 family trip to Nagasaki and Huis Ten Bosch. Markdown and YAML in GitHub held the plans, reservations, expenses and packing information; a Next.js site on Vercel displayed the latest version.
note.com
Original prompt
Shared by the source author. See source notes for context.
8月2日のGmailから、ハウステンボスの1DAYパスポート購入内容を読み取って反映して
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- billest｜AI ×人生OS
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The completed trip used live replanning and expense updates; sharing the app did not result in broad independent family use.
- Human involvement
- Billest chose the bus and other changes, corrected location errors and acted as the information hub for his family.
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
- Import confirmed reservations into linked itinerary and expense records.
- Send changed transport timing and local photos to revise the plan.
- Record receipts and family preferences while preserving the underlying trip files.
Billest built Travel OS eight days before an August 9 family trip to Nagasaki and Huis Ten Bosch. Markdown and YAML in GitHub held the plans, reservations, expenses and packing information; a Next.js site on Vercel displayed the latest version.
Claude Code read Gmail confirmations and propagated details into related sections. Importing a park ticket updated the reservation, itinerary and cost records together. During the trip, an airport bus gap forced a decision: the next service after 13:05 was 14:45, so the family skipped the planned airport lunch and boarded the earlier bus. From the bus, Billest asked Claude to reorganize lunch, luggage storage and check-in.
Photos supplied missing local context. A photographed map corrected an initial location mix-up; receipt photographs fed the expenses page, which was later changed to category summaries and expandable details. The author also recorded practical mistakes immediately, including a rejected oversized battery and a breakfast choice that did not suit the family.
Sharing the site did not mean everyone used it. His wife mostly left the information gathering to him, and he passed the relevant details along. The completed-trip result is a live information hub and recorded family preferences. Its promised value on later trips had not yet been demonstrated.
Prompt
Original prompt
Source: note.com · billest｜AI ×人生OS
Frequently asked questions
Did the family all use the app?
No. His wife mostly did not open it during the trip; Billest consulted it and relayed the useful information.
Why update several records from one confirmation?
A reservation changed timing and costs together, avoiding separate manual copies across those sections.
Were next-trip benefits already proved?
No. The author considered reuse on later trips the next test of the recorded lessons.
More details
About this account
Claude Code edited the Markdown trip records, propagated reservations and expenses, and updated the deployed travel site.
Firsthand source opened and read. Prompt is a verbatim excerpt of the published original instruction.
Credit: billest｜AI ×人生OS
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude Code · Gmail · GitHub · Next.js · Vercel
Live itinerary changes · Reservation imports · Family trip records
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.