Book flights and hotels, stopping at payment for approval
claude. Task: claude cowork travel productivity beginner Co-founder at King’s Cross Labs · ex-LinkedIn PM & Forbes 30 Under 30 Send this guide to yourself Get the link in your inbox so you can read it whenever you're ready. Your email will also be saved for future updates. Boris Cherny, the creator of Claude Code, recently had Claude Cowork book 8 flights and 5 hotels for him while he kept working in Claude Code. With Opus 4.7, he said it one-shotted the whole thing. I'm not promising you'll never touch a booking site again. But you can get close: research in Claude, book in your browser, and approve before anything gets charged. Building with social media and ads APIs? I'm currently building Adeli! We help builders and founders connect theirusers to social media and ads platforms through one API. Creator, agency, or marketer? Use it to see all your social and ads metrics in one place. Why this matters This only works if you set it up once. Claude needs permission to use your browser, connectors to search flights, and a project that knows your seat preferences, loyalty numbers, and hard rules (like "never book without asking me"). After that, each trip is a short prompt instead of an afternoon of tab-hopping. Key insight: You're not handing Claude your credit card and walking away. You're building a flight-booking assistant with two approval gates: one before it starts booking, and one before it clicks purchase. Get the browser and connectors ready Step 1: Set up Claude in Chrome Download the Claude in Chrome extension. It's a browser extension that lets Claude navigate, click, and fill forms in Chrome. That's how Cowork actually completes bookings on airline and travel sites. In the Claude desktop app, go to Settings → Claude in Chrome (Beta) → General and turn on Allow all browser actions. Without this, Claude will stop and ask permission on every click. For flight booking, you want it to move through search and checkout smoothly, then pause only when it's time for you to approve payment. Step 2: Connect Expedia Connectors let Claude search flights from inside Claude before it opens the browser to book. Go to Settings → Connectors and connect Expedia. Set interactive tools like Flight Search to Always allow so research doesn't stall mid-trip. Expedia works well if you already log into the site. Claude can also book through Google Flights in the browser when that's the better path. Build your Flight Booker project Step 3: Create a project with your flight preferences In Claude Cowork, create a project called Flight Booker. Paste the instructions below and replace every [BRACKET] field with your real details: legal name, home airport, seat rules, loyalty numbers, and card last four digits only. This is the same idea Boris used: put your preferences in instructions once, then every booking session inherits them. Book a trip Step 4: Tell Claude what flight you want Open your Flight Booker project and send a short trip prompt. The project instructions already cover preferences, so you only need route, dates, and priorities. For a single trip: For multiple trips (conference travel, wedding season, a packed quarter), do what Boris did: point Claude at the emails or calendar invites with your itineraries. Ask it to extract dates, cities, and deadlines into one list, then work through bookings one by one (or in batch if you're comfortable approving each option). Step 5: Let Claude Cowork book in Chrome Once you approve an option ("Book option 1"), Cowork opens your browser, searches on Expedia or Google Flights, navigates to the airline or booking site, fills traveler details from your project instructions, picks seats, and stops at the payment screen. You'll see it working in a Cowork browser window. You can watch live or ignore it until Claude asks for final approval. Boris described it as "I let Opus get to work" while he kept hacking in Claude Code. Before anything charges your card, Claude should show you the final total, baggage rules, and cancellation terms. Only say "Go", "Confirm", "Purchase", "Book it", or "Yes, charge it" when you're ready. After booking, you should get a clean confirmation summary (confirmation code, seat, total charged) from your project instructions. Safety first 1. Sensitive information needs a real strategy; tools: Claude Cowork, Claude in Chrome. Human role: The original post does not say how a person stayed involved.; limitations: Requires one-time setup of browser permissions, connectors, and detailed project instructions. The author notes Claude in the browser can be 'finicky' and may require trial and error. Handling sensitive payment information is high-risk; the source recommends using secure credential managers like 1Password for agents rather than pasting card details into chat..
Tools
Published on Agent Work Atlas:
Overview
claude
Workflow
claude cowork travel productivity beginner Co-founder at King’s Cross Labs · ex-LinkedIn PM & Forbes 30 Under 30 Send this guide to yourself Get the link in your inbox so you can read it whenever you're ready. Your email will also be saved for future updates. Boris Cherny, the creator of Claude Code, recently had Claude Cowork book 8 flights and 5 hotels for him while he kept working in Claude Code. With Opus 4.7, he said it one-shotted the whole thing. I'm not promising you'll never touch a booking site again. But you can get close: research in Claude, book in your browser, and approve before anything gets charged. Building with social media and ads APIs? I'm currently building Adeli! We help builders and founders connect theirusers to social media and ads platforms through one API. Creator, agency, or marketer? Use it to see all your social and ads metrics in one place. Why this matters This only works if you set it up once. Claude needs permission to use your browser, connectors to search flights, and a project that knows your seat preferences, loyalty numbers, and hard rules (like "never book without asking me"). After that, each trip is a short prompt instead of an afternoon of tab-hopping. Key insight: You're not handing Claude your credit card and walking away. You're building a flight-booking assistant with two approval gates: one before it starts booking, and one before it clicks purchase. Get the browser and connectors ready Step 1: Set up Claude in Chrome Download the Claude in Chrome extension. It's a browser extension that lets Claude navigate, click, and fill forms in Chrome. That's how Cowork actually completes bookings on airline and travel sites. In the Claude desktop app, go to Settings → Claude in Chrome (Beta) → General and turn on Allow all browser actions. Without this, Claude will stop and ask permission on every click. For flight booking, you want it to move through search and checkout smoothly, then pause only when it's time for you to approve payment. Step 2: Connect Expedia Connectors let Claude search flights from inside Claude before it opens the browser to book. Go to Settings → Connectors and connect Expedia. Set interactive tools like Flight Search to Always allow so research doesn't stall mid-trip. Expedia works well if you already log into the site. Claude can also book through Google Flights in the browser when that's the better path. Build your Flight Booker project Step 3: Create a project with your flight preferences In Claude Cowork, create a project called Flight Booker. Paste the instructions below and replace every [BRACKET] field with your real details: legal name, home airport, seat rules, loyalty numbers, and card last four digits only. This is the same idea Boris used: put your preferences in instructions once, then every booking session inherits them. Book a trip Step 4: Tell Claude what flight you want Open your Flight Booker project and send a short trip prompt. The project instructions already cover preferences, so you only need route, dates, and priorities. For a single trip: For multiple trips (conference travel, wedding season, a packed quarter), do what Boris did: point Claude at the emails or calendar invites with your itineraries. Ask it to extract dates, cities, and deadlines into one list, then work through bookings one by one (or in batch if you're comfortable approving each option). Step 5: Let Claude Cowork book in Chrome Once you approve an option ("Book option 1"), Cowork opens your browser, searches on Expedia or Google Flights, navigates to the airline or booking site, fills traveler details from your project instructions, picks seats, and stops at the payment screen. You'll see it working in a Cowork browser window. You can watch live or ignore it until Claude asks for final approval. Boris described it as "I let Opus get to work" while he kept hacking in Claude Code. Before anything charges your card, Claude should show you the final total, baggage rules, and cancellation terms. Only say "Go", "Confirm", "Purchase", "Book it", or "Yes, charge it" when you're ready. After booking, you should get a clean confirmation summary (confirmation code, seat, total charged) from your project instructions. Safety first 1. Sensitive information needs a real strategy
Reported result
The source cites Boris Cherny using this workflow to book 8 flights and 5 hotels in one run with Opus 4.7. However, the author states they have only performed the research step and not the payment step personally. No measured success metrics or error rates are provided for the general user base.
Human role
The original post does not say how a person stayed involved.
Limitations
Requires one-time setup of browser permissions, connectors, and detailed project instructions. The author notes Claude in the browser can be 'finicky' and may require trial and error. Handling sensitive payment information is high-risk; the source recommends using secure credential managers like 1Password for agents rather than pasting card details into chat.
Try it
Act as a travel booking assistant using Claude Cowork and Claude in Chrome. First, verify that the 'Allow all browser actions' setting is enabled and the Expedia connector is active. Create a project named 'Flight Booker' with my preferences: [replaceable inputs: home airport, seat preference, loyalty numbers, hard rules]. For the trip [replaceable inputs: origin, destination, dates, priority], research 3 flight options via the connector. Present them with total price, baggage rules, and cancellation terms. Wait for my explicit approval of one option. Then, use the browser to navigate to the booking site, fill in traveler details from the project, and select seats. Stop immediately before the final payment button. Show me the final total and any changes from the research quote. Do not click purchase until I say 'Confirm'. If any sensitive data is missing, ask me for it. If the browser flow fails, explain the error and suggest the next best path.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.