Keyboard

Shortcuts

Global

?Show this listapp routes— Other screen
CtrlKSearchwherever the search panel mounts— Other screen
EscClose the top layer✓ Available here

Trip

16Open a tool by positionTrip page, design fixture— Other screen
Move along the railThe trip page rail— Other screen
nAdd an itemAdds a trip on the trips list— Other screen
uUpload a documentThe trips list— Other screen
aShow or hide archived tripsThe trips list— Other screen

Editing

CtrlBBoldWhile the cursor is in a note— Other screen
CtrlIItalicWhile the cursor is in a note— Other screen
Stub

Search

One index across every trip you've added

Every trip you've added lives in one search — typed into the box, or asked by your own AI over MCP, and read-only either way.

Two trips, two hits, each keeping its own trip attached.

Search every trip at once

/search is one box over every trip you've added — not the trip you currently have open. Type a hotel name, a confirmation number, a city, and it matches as you type, the same typeahead the rest of the product uses.

It searches trips and the items inside them, together, in one pass.

Every result keeps its trip attached

A result is never just a title. Each row names the trip it came from and when — a boarding pass three trips back still says which trip it belongs to.

An item with a confirmation number carries it on the row, ready to copy.

Your AI can search your trips, and only search them

Your own AI — Claude, Codex, anything speaking MCP — gets the same job through trip_search, and it's READ ONLY: one of exactly five tools, in a toolset of twenty-six, that can't write to a trip.

It's not the same index as the web page — trip_search matches items, not the trip records themselves, and it doesn't complete-as-you-type the way the web box does. Your AI can find the boarding pass; it can't rename the trip.

Where it lives

MCP tool
trip_search — read only
Search your trips

New here? Signing in creates your Miles account.

All features