Google shipped another batch of AI Mode updates and the travel ones took the headlines: track flight prices, help book hotels, find a table. I read through it expecting to be annoyed, and I was, though not for the reason I went in with. The features are fine. The demo is smooth. But every one of them stops at the same wall, and Google isn’t pretending otherwise.

It walks you to checkout and then shrugs

Watch where the flow actually ends. AI Mode surfaces options, compares rates, narrows twelve hotels down to three, and then gives you a link. You click it. You sign in. You pick a card. You dig up the Hyatt number that lives in a note on your phone because you have never once remembered it.

The model did the research. You did the booking.

That split isn’t a rollout gap that gets closed next quarter. It’s structural. Google’s agent is running a session that has never been logged into your Marriott Bonvoy account, doesn’t know your TSA PreCheck number, has no idea that you always book the aisle, and cannot see the card you keep for travel versus the one you keep for everything else.

Loyalty numbers are the boring detail that breaks everything

Booking is a bad task for a logged-out agent because almost none of the inputs are public. Price is public. Availability is public. Everything that turns a search result into a reservation lives behind a login: your status tier, the free-night certificate expiring in November, the second traveler whose passport number sits in the airline’s saved-travelers list and nowhere else you can retrieve in under four minutes.

So the agent optimizes on the one variable it can see, which is price, and hands you back a result that’s frequently wrong for you. A $310 room at a chain where you have zero status is not better than a $340 room where you’re two nights from re-qualifying. Google’s agent can’t know that. It’s not a reasoning failure. It genuinely does not have the data.

Corporate travel makes it worse

A large chunk of people reading this can’t book on the open web anyway. There’s a Navan or Concur or Egencia instance sitting between them and every flight, loaded with negotiated rates, a policy engine that rejects anything over $400 a night in Chicago, a cost center field, and an approver who has to click something before the ticket issues. None of that has a public URL. None of it has an API you can get access to without a six-week IT conversation, and if you’re at a company where procurement owns that relationship, you will not be the one who gets it approved.

An agent that hands you a link to hotels.com is useless in that world. The work isn’t finding the hotel. The work is the eleven fields in the corporate portal after you’ve found it, which is exactly the kind of grinding, low-stakes, high-annoyance task nobody should be doing by hand in 2026. I’ve written before about how cloud agents can’t see that you’re logged in, and travel is the cleanest example I’ve found. The gap between “knows about hotels” and “can book your hotel” is entirely session state.

A side panel is already inside the session

This is the part where the framing flips. If the agent runs in your browser instead of on Google’s servers, the whole authentication problem evaporates, because you already solved it. You logged into Navan on Tuesday. The cookie is right there.

Dassi sits in the Chrome side panel and works in the tab you have open. Point it at the corporate booking tool and it fills the traveler details, the cost center, the policy justification box, and stops before it commits. Ask it to check whether the flight you’re holding still matches the fare tracked last week, and it reads the page you’re looking at, not a cached scrape of a public rate.

Same models underneath. Google’s Gemini, or Claude, or GPT, whichever you point at it. The model was never the bottleneck here.

Where I’d still keep my hands on the wheel

I don’t want any agent hitting confirm on a $2,400 international ticket without me. Dassi asks. That’s the design, and I’d be suspicious of a tool that didn’t, because the failure mode of an autonomous booking agent is not a wasted minute, it’s a nonrefundable fare on the wrong date.

But there’s a damn wide gap between “book it autonomously” and “hand the human a link and let them do the last nine steps.” Google picked the second one because their session is a stranger to your accounts. It’s the only option they have. Their AI Mode integrations have the same shape everywhere else too.

The travel agent that actually finishes the job isn’t going to live in Search. It’s going to live one panel over from the tab where you’re already signed in, which is a much less exciting sentence than “agentic commerce,” and considerably more useful on a Tuesday afternoon when you’re trying to get to Denver.