Lesson 9
Estimated time: 10 minutes
Learning objectives
By the end of this lesson you'll be able to:
- Recognize the kinds of work Claude in Chrome unlocks
- Use Chrome alongside Cowork on a real piece of work
Watch it work
The video shows how Claude can work in Chrome to read, click, and navigate websites alongside you.
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.
Cowork prompt
“Pull yellow and red accounts from the customer-health dashboard for the last 30 days, then build a one-page summary with the top three at-risk accounts.”
Customer health
Cowork takes it from here
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.
A few watch-outs
- You need to be signed in. Claude can't sign in to a tool for you. If the dashboard requires authentication, you log in once in your browser; Claude works in the session you're already authenticated in.
- Be deliberate about what you give Claude access to on the web. Just like with connectors, Claude sees what you see — but on the open web, that includes anything you have access to. For sensitive sites, narrow what Claude can act on, and review the actions before approving them.
To find the latest setup guidance, see Get started with Claude in Chrome.
Try it now
Pick one task on your plate that lives in a browser-based tool that doesn't have a connector. Open Cowork, describe the task, and let Claude work in Chrome, then hand off insights to Claude in Cowork.
What’s next
In the next lesson, you'll see Claude show up inside the M365 apps where a lot of work actually lands — Word, Excel, PowerPoint, and Outlook.