When should you use it?
- You book trips for the same people repeatedly
- Preferences live in someone's head
- You want lessons from bad trips to stick
Not for: Booking and paying without approval; Travelers whose data you cannot store
What do you need, and what do you get?
You need
- Traveler profiles and preferences
- Hermes Agent, with its built-in memory and search
- A debrief habit after each trip
You get
- Itinerary recommendations
- Visa status checks
- Updated traveler rules after each debrief
How does it work, step by step?
- Write the persona and contextGive the agent a short role description and the domain rules it should know.
- Store preferences in memorySeat, meals, hotel areas and limits for each traveler.
- Plan with web searchAsk for one recommended option that applies every stored preference.
- Debrief after travelDescribe what went wrong; a debrief skill turns it into a dated rule.
- Re-plan and confirmCheck the next plan cites the new rule.
The prompt
Our own prompt, inspired by Christopher Mburu and written to work in Custom agent. Values in lime are placeholders.
Plan a trip for [traveler] to [city] on [dates]. Read their preferences from memory and apply all of them without asking. Search flights and hotels, then give one recommendation with the reason each preference is met, plus one backup. Check visa requirements. After the trip, I will give a debrief: turn it into a dated rule and show me the memory change before saving.
Inspired by Christopher Mburu: Hermes TravelOps: An Agent That Learns From Every Trip. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- The author seeded demo data; real traveler records need privacy care.
- Searched fares change quickly, so confirm before booking.
Our take
The debrief loop is the reusable idea here, more than any particular agent stack. Most travel tools forget; writing a dated lesson after every trip is what a good assistant does by habit. Review each memory edit before it takes effect, since a bad rule silently shapes every later plan. Keep passport numbers, loyalty credentials and payment details out of memory files; store those in a real secrets vault. Seed demo profiles carefully so test data never mixes with your real preferences. Prefer non-stop suggestions when the memory says so, but still compare price and arrival time yourself. Confirm visas and entry rules from official sources, not the agent's summary. After each trip, force a short debrief even when nothing went wrong, so good habits get recorded too. Cap how aggressively it can rewrite preferences in one pass. Keep currency and loyalty program choices explicit in the persona file. Confirm hotel cancellation windows before locking a plan.
Where the time goes back: Coordinators stop restating each traveler's needs, and mistakes from one trip shape the next automatically.
FAQ
Does it book?
Where is memory kept?
Source and credit
Inspired by Christopher Mburu. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Hermes TravelOps: An Agent That Learns From Every Trip
- Creator
- Christopher Mburu
- Published on
- DEV Community (dev.to)
- Original date
- May 31, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.