Track booked travel price drops
Monitor already-booked flights or hotels for automated refund requests.
Identify accessible lounges and nearest gates during long layovers.
A curated list of eligible terminal lounges with walking times from your arrival gate.
"During a long layover in Boston, Muse knew which credit cards the author owns and where the connecting gates were, which made the 3-hour layover a bit less painful."
The author must provide Muse with their credit card information and flight/connection details.
Manual paste in chat
Review authorization prompts carefully before connecting.Review generated values, dates, or messages before executing binding transactions or payments.
Gather materials: The author must provide Muse with their credit card information and flight/connection details.
Copy the prompt template below, substituting bracketed text like [date range] or [account details] with your real information.
Paste into your Muse session. Watch for required tool authorizations or review prompts.
Compare generated figures, dates, or communication drafts against your original records before taking binding actions.
I have a 3-hour layover in Boston. The credit cards I own are: [list of cards]. My connecting flight departs from gate [gate number] at [time]. Plan how I should spend the layover: which airport lounges I can access with my cards (and their locations relative to my gate), where to eat nearby, and how much buffer time to leave for getting back. Present the plan ordered by time, include walking-time estimates, and flag anything that might change (such as gate changes). Do not book or pay for anything without asking me first.
Before relying on the output or confirming irreversible actions, run these targeted verification checks:
If third-party service connections fail or require permissions, inspect your account tokens.
Check Connections & permissions guide →If large context blocks cause partial truncation, break input into smaller batches.
Review token caps in Access & limits →