Get a booking out of your inbox
You book on the airline's own site, the way you always have. The confirmation lands in your mail. Forward it to your Stub address and the extractor reads the segments out of it, the same way pasting the text into a trip does. There's nothing to install and no mailbox to connect.
It arrives in the band at the top of your trips, with the trips whose dates it overlaps offered first. Filing it is one tap. Stub doesn't pick the trip for you — matching a booking to a trip off free text is a guess, and a wrongly-filed booking is worse than an unfiled one. Forward the same confirmation twice and you get one item, updated.
From there it's on the trip, and everything the trip feeds has it: the timeline it sits on in order, the map of where you'll be, and the search that runs across every trip you've added.
It's in your calendar too, if you subscribed one. The feed is built fresh on every fetch and covers every trip you're on, so the booking is there the next time your calendar refreshes — nothing to export again, nothing to re-import. Stub asks calendar clients to hold their copy for up to an hour, so the update lands on their schedule rather than the moment you file it. Calendar follows that one down. The only thing you did was forward a message and tap once.
Plan the connection before you land
Two flights that meet at the same airport are a connection, and Stub works out the gap between them and how tight that makes it. That part happens on its own, on the timeline, the moment both legs are on the trip.
Ask Miles to plan it and it reads both flights from the trip. You get the terminal change, whether you clear immigration again, and the estimated minimum connection time.
A gap with no way from the airport to the hotel gets named options — the Narita Express, the Heathrow Express — with cost ranges. Ranges, never a quote. Those are proposed for you when the trip changes; the layover plan is the one you ask for, one connection at a time.
The plan is advice you check, not a guarantee. Connection times are estimates, terminals move, and the model writing the advice is sometimes wrong — confirm on the arrivals board before you count on it.
Hand the trip to the people on it
Travelers are the people the trip is for. Put someone on the roster and their name rides on the trip and its items, so a booking says who it's for rather than only what it is.
A household grant is standing access, for the people who should have it: one switch per person, on until you revoke it, covering your trips rather than one of them.
A share link is for everyone else — the friend meeting you there, the person watching the house. It's read-only by construction, not by policy: the server builds a smaller payload than the app's own and sends that. Schedule, places, and a flight's route and cabin cross. Confirmation numbers, costs, points, award certificates, seat numbers and your notes are not hidden on the page — they are never sent. The link is also marked no-index and sends no referrer, so a click out of it can't leak the URL. Sharing follows that one all the way down.
Bring your own AI
Stub speaks MCP. Point Claude or Codex at one server URL and your own AI can ask about your own trips — the same twenty-six tools the rest of the product is built on, so what your AI can do and what the app can do can't drift apart.
Connect a second one and they answer in the same thread. Stub knows the itinerary. Miles knows the wallet. Your AI does the chaining, and the labels below say which system each answer came from.
What's on the Tokyo trip?
March 10–17. Flights out through Haneda, four nights at the Park Hyatt, three places, and one to-do.
Was the flight a good redemption?
75,000 points plus $5.60 in taxes, against a $2,140.00 cash fare. That's 2.85¢ per point.
Do my cards get me a lounge in the Haneda connection?
The Platinum Card carries Centurion Lounge and Priority Pass. The ANA Lounge comes with your business cabin on the Star Alliance entitlement — verify at the desk.
Anything still free to cancel, on any trip?
The Park Hyatt, until Sep 28. The flight is past its free-change window.
Add a to-do to reserve the Narita Express.
Added to the Tokyo trip.
Four of those five calls are Stub's own, named the way the AI makes them. trip_read, trip_budget and trip_search are three of the five tools, out of twenty-six, that can't write to a trip. trip_todo_add is the last one, and it's the one that needs permission you grant separately, on the approval screen — read-only unless you allow writes.
Item titles and notes originate in forwarded email, so everything Stub hands back is marked as untrusted content before your AI reads it. That is a hint to the model, not a guarantee about it.
The pieces, each doing one job
Nothing above is a mode you switch on. Each chain is ordinary parts, in order, and every part is worth understanding on its own.
- Forwarding
- A per-user address that turns a confirmation email into an item. Forwarding →
- Unfiled band
- Where a new booking waits, with the trips whose dates it overlaps offered first.
- Map
- The trip's stops on one map, in the order you'll reach them. Map →
- Calendar feed
- One subscription per person, covering every trip they're on. Calendar →
- Layover plan
- Reads both flights and names the terminal change, re-clear steps, and estimated minimum connection.
- Transfer options
- Named ways from the airport to the hotel when nothing bridges the gap, with cost ranges.
- Share link
- A redacted copy of the trip for somebody who has no account. Sharing →
- Search
- One index over every trip you've added, typed or asked. Search →
- MCP server
- One URL and twenty-six tools, read-only unless you allow writes. Connect →
Where the chains stop
- Nothing here books anything. Stub is a readable copy of your bookings, not the bookings themselves. Check with the airline or hotel before you travel.
- Stub never picks the trip for a forwarded booking. It offers the ones whose dates overlap and waits for you. That is a decision, not a missing feature, and it is not going to change.
- A tight connection is flagged on its own; the plan is not. Detection runs for you. Planning is something you ask for, one connection at a time.
Every chain here runs on parts that ship today. Each section says where its chain stops. Features takes each part on its own, and Securitysays how your trips are protected, and what is not.
New here? Signing in creates your Miles account.