Claude in Chrome

In this lesson, you'll recognize the kinds of work Claude in Chrome unlocks and use Chrome alongside Cowork on a real piece of work.

Key takeaways

• Claude in Chrome is the bridge for tools that don't have a connector. For anything that lives in a browser, Claude can read and act on those pages.
• Claude in Chrome and Cowork work together. Claude can gather info and take actions in the browser; it then takes the results and builds the deliverable back in Cowork. One conversation, both surfaces.
• You stay in control. By default, Claude in Chrome asks before sensitive actions, and you can approve or deny each one.

What this unlocks

A few examples that matter in real work:

• Internal dashboards. Your finance team's Tableau view, your sales ops Looker dashboard, the BI tool with the metric you check every Monday. Claude can pull the numbers, download them to your computer, and use that context for Cowork tasks.
• Vendor portals and customer systems. The procurement portal that doesn't have an API. The CRM that's behind your single sign-on. The customer support tool where every ticket has to be triaged. Claude can navigate the portal, pull what you need, and act on it the way you would.
• Web apps behind a login. Anything with a browser interface — even tools your team built — becomes scriptable. "Open the procurement system, find every PO from our top ten suppliers in Q3, and pull the line items into a spreadsheet."
• Web research that ends in a deliverable. Open ten tabs, pull what's on each, and turn it into a brief — without copy-paste.

The pattern: any time you'd find yourself thinking "I'd love to give this context to Claude, but it lives on the web," Claude in Chrome is the answer.

Use it with Cowork

A real example: your team's customer health dashboard lives behind a login and doesn't have a connector. You want a one-page summary of every account showing yellow or red, by Friday.

In Cowork, you say:

Open the customer health dashboard in Chrome, pull every account showing yellow or red, and for each one, pull the past 30 days of activity from the customer's folder in Drive and recent threads in #customer-success in Slack. Build a one-page summary I can review before my Friday call.

Claude hands the browser steps to Claude in Chrome, takes the data back, pulls the supporting context from Drive and Slack, and builds the summary in your folder. One delegation, three sources of context.