Key points
- Gemini app adds a Task mode that makes calls, books appointments, analyzes bills and checks out purchases, switched on via a Chat-to-Task toggle.
- Rollout is free in the U.S., Japan, Korea, Canada, Australia and India on the new Gemini 4 Hydrogen model; advanced features start in the U.S.
- Purchases run on the Agent Payments Protocol with Mastercard and Visa tokens, American Express coming soon; users can set a hard spending cap.
- Gemini connects with more than 60 apps, and developers can apply to the Connected Apps Platform.
Why it matters for marketers: Agent-led shopping, booking and checkout through Gemini will shape how customers find and buy, so marketers need their product data, sites and payment flows ready for assistants.
Google has updated the Gemini app so it can carry out multi-step chores rather than only answer questions. Users flip a toggle from Chat to Task, text Gemini, or forward emails to [email protected]. In examples from Josh Woodward, Google's VP of Labs, Gemini called two dealerships at once to book a service visit, analyzed past utility bills, bought a charger and added items to an Instacart order.
The update is free in six countries and runs on Google's new Gemini 4 Hydrogen model, with advanced features starting in the U.S. Shopping uses the Agent Payments Protocol, with Mastercard and Visa supported and American Express coming. Receipts land in Google Wallet, which expands to iOS. Google says Universal Commerce Protocol support is next.
For marketers, the notable shift is that discovery and checkout can happen inside an assistant using Google's Shopping Graph, with the user never visiting a brand's site. Google says Gemini discloses that it is an AI when it calls businesses, and businesses can opt out. Local and service businesses should expect calls from agents, and retailers should expect agent-driven carts.
Google also acknowledges limits. Tasks can fail, and on some sites Gemini hands the screen back for the final click. The company says it is working with major websites and security providers on open, verifiable standards for assistants. Teams should watch how those standards develop, check that product feeds and booking flows work for automated visitors, and review how their bot-blocking rules treat legitimate assistants.
Sources
This brief is our own summary. Read the full reporting at the source.
