What is Trip.md

Trip.md is a single markdown file that holds everything tied to one journey: where you’re going, when, and what’s booked so far. It’s the companion to Traveler.md. Where Traveler.md is the constant (how you travel, every trip), Trip.md is the moment (this trip, right now).

You create a new Trip.md per trip and update it as plans firm up. When the trip is over, it’s a record of what happened; while the trip is live, it’s the shared workspace an agent reads from and writes to.

The shape, at a glance

A Trip.md file is plain markdown with conventional sections. An agent can parse it reliably, and you can open it and adjust a line when plans change.

Trip.md

# Trip: Lisbon
 
## Dates
In Lisbon from March 12 to 16, 2026.
 
## Status
Flights are booked and the hotel is being held.
 
## Itinerary
Four nights near the centre, with a vegetarian dinner planned close to the hotel.

How it works with Traveler.md

An agent generally loads Traveler.md once per session and the relevant Trip.md when one is in flight. Together they give a complete picture: Traveler.md says you take the window seat and don’t eat meat, Trip.md says this particular trip is four nights in Lisbon with the outbound flight already booked.

Agents never touch the file on disk. They connect to the Traveler.md MCP server, which owns storage, enforces the scopes you granted, and hands back parsed structured data.

What it is not

Not your preferences. Anything true across every trip (seat choice, loyalty programs, dietary needs) belongs in Traveler.md, not here.
Not a booking system. Agents and partners do the booking. Trip.md records and coordinates what’s planned.
Not permanent. You have one Traveler.md and as many Trip.md files as you have trips. Each one is scoped to a single journey.