Traveler.md vs Trip.md

Traveler.md and Trip.md are sister formats. Both are markdown, both flow through the same MCP server, and both can be edited by a human or an agent. The difference is lifespan and scope.

Traveler.md: the constant

The things about you that hold steady from trip to trip:

• Identity (preferred name, passport country, home base)
• Travel style (window vs aisle, redeye tolerance, hotel category)
• Loyalty programs and elite status
• Dietary needs and accessibility requirements
• The people you regularly travel with

You update it occasionally. Agents read it on almost every interaction, because it’s the answer to who am I serving?

Trip.md: the moment

Everything tied to one specific journey:

• Destinations and dates
• Confirmed bookings: flights, hotels, transfers
• Itinerary items and reservations
• Decisions made, and options still open
• Who’s coming on this trip

A Trip.md is created when planning starts and written to constantly as plans firm up. When the trip ends, it becomes history. A traveler keeps one Traveler.md and accumulates many Trip.md files over time.

Which file does this belong in?

The test: would this still be true on your next, unrelated trip? If yes, it’s Traveler.md. If it only matters for one journey, it’s Trip.md.

Agents usually load both: Traveler.md for who, the active Trip.md for what. They’re reached through the same MCP tools but separate scopes, so you can let an assistant read your preferences without giving it your trips, or the reverse. See Authentication for the scope catalog.