← Back to library

Plan business trips with memory that learns from debriefs

Christopher Mburu built a travel operations agent on Hermes for a challenge. Skills cover planning and post-trip debriefs; traveler preferences live in a Markdown memory file. After a debrief about a six-hour layover, the agent itself wrote a three-hour maximum into memory and the next Dubai plan chose a non-stop. Demo profiles were seeded.

  • OutcomeGet itineraries that already respect each traveler's quirks, plus a debrief step that updates those rules so the next plan avoids the last trip's problems.
  • SetupAn afternoon+
  • LevelIntermediate
  • CreditChristopher Mburu
View original
Works with
Custom agent

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

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?

  1. Write the persona and contextGive the agent a short role description and the domain rules it should know.
  2. Store preferences in memorySeat, meals, hotel areas and limits for each traveler.
  3. Plan with web searchAsk for one recommended option that applies every stored preference.
  4. Debrief after travelDescribe what went wrong; a debrief skill turns it into a dated rule.
  5. 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.

Prompt0 variables
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?
No. It recommends, checks visas and updates memory; booking stays with a person.
Where is memory kept?
In the agent's own Markdown memory file, which the debrief rewrites directly.

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.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Add a merge check for every way coding agents break code

Keep a running list of the specific ways coding agents have damaged your repository, from hollow tests and invented fake responses to deleted files and silenced type errors, and turn each one into an automated gate that blocks the merge, so the same mistake cannot slip through review twice.

Credit: u/alexmarquardt on r/ClaudeCode

An afternoon+
Operations & AdminPrompt✓ AI dry run

Audit how you manage your agent team, not only the agents

Have your chief-of-staff agent review the last 30 days of how you delegated, clarified, interrupted, corrected, assigned, approved and followed up across your agent team, score eight management areas with evidence, list your three biggest weaknesses, and draft a seven-day improvement plan, without changing any bot, routine or instructions until you approve.

Credit: Michael Fenech (@Michael_Fenech_)

Under an hour
Operations & AdminPrompt✓ AI dry run

Audit how your agents pick tools before buying more usage

Have your lead agent review the recurring jobs it can see, note which apps, scripts, browser sessions or full computer control each one relies on, flag jobs that take a heavier route than needed or rely on remembered facts, check permissions and fallbacks, and then propose three side-by-side experiments before anything is changed.

Credit: Michael Fenech (@Michael_Fenech_)

Under an hour
Operations & AdminWorkflow✓ AI dry run

Give Codex a research-folder instructions file

Open your research project folder in Codex, add a plain-language instructions file about role, standards, style and critique, and save every big result as a file.

Credit: Mushtaq Bilal, PhD (@MushtaqBilalPhD)

Under an hour