When Claude says it cannot reach a website, it usually can
If Claude tells you it cannot log in, cannot see a dashboard or cannot reach a site, that is usually a limit of the session you are in, not a limit of Claude. Open the same page in Chrome and ask again.
That one distinction opens up most of the tools people assume are off limits.
Two places Claude works, and which to use
Once you are set up, there are two different ways to put Claude to work, and they are good at different things.
Your Claude Code session is for your files, your emails, your calendar and anything you have connected properly. It is the deep, permanent connection and it is where most of the work happens.
Claude in Chrome is for any website in your browser, especially the ones you log into that have no connection available. Claude sees what is on the page and acts on it there.
The decision rule is simple: if it is connected, use your Code session. If it is a site you log into and there is no connector for it, open it in Chrome.
The tools this covers
Most business software has no connector, and never will. That is the gap Chrome fills.
- Seller and marketplace portals. The Iconic Seller Centre and equivalents.
- Fulfilment and shipping dashboards. ShipHero, DHL.
- Invoicing tools. invoice2go.
- Banking and payments. Airwallex.
- Receipt and bookkeeping apps. Hubdoc.
- Social platforms. Instagram.
Booking systems, supplier portals, internal dashboards, web forms. If you log into it in a browser and there is no connection for it, that is the Chrome path.
Push back, and do not take no for an answer
This is the part worth remembering.
Claude Code will sometimes tell you it cannot do something. It cannot reach that site, it cannot log in, it cannot see that dashboard. People read that as a hard limit of the product and stop.
Usually it is a limit of the code session only. The same task, on the same site, with the page open in Chrome, works.
Cases where this comes up constantly:
- Logging into a portal you have a perfectly good account for
- Reading a dashboard that only exists on screen
- Filling in a web form
- Pulling information out of a site with no connection set up
When you hit a no, do not accept it. Move to Chrome and ask again.
It asks before it acts
The obvious worry about letting an AI use your browser is that it clicks something it should not, on a site where that matters.
Claude shows you what it is about to do and waits for your okay. It will not click, type or submit anything without you confirming first. You watch the action before it happens and approve it.
That is what makes it usable on a banking dashboard or a live seller portal rather than only on things that do not matter.
A good first task
Pick a website you use regularly that is not connected to anything. Something you log into. A supplier portal, your invoicing tool, a booking system.
Open it in Chrome and ask Claude to pull something useful out of it, or to fill something in for you. Watch it work through the page and ask before each step.
Most people’s reaction is not that it is clever. It is that they had been doing that by hand every week for years.
This is Step 12 of Saviwith Foundations, the bonus step. The course gives you the prompt that installs and configures Claude in Chrome, walks the setup with you, and shows a recording of a real task being done on a live website start to finish.
Thirteen steps, at your own pace, lifetime access.
Start your course now · $497