Every company has one of these: a portal with no API, no export you can schedule, nothing to plug an integration into. A supplier's ordering site, a benefits admin login, a government filing form. Every week, someone logs in, clicks through four or five screens, downloads a report, and pastes the numbers somewhere else. It's five minutes, so it never made the list of things worth automating — and it's still happening by hand, every single week, a year later.
Why this chore never got an automation
A script could click through a web page the way a person does — that's not new. Tools for it have existed for years. But writing and maintaining one is real engineering work: it breaks the day the portal moves a button, needs someone who can code to fix it, and costs more setup time than the five minutes a week it saves. Nobody signs up to own that trade for a chore this small, so it stays manual, and stays exactly the kind of task that quietly depends on one person remembering to do it.
What changed
Claude in Chrome is a browser extension — reached general availability on 26 August 2026, on the Pro, Max, Team and Enterprise plans, Chrome only (not Edge, Brave, Arc, or mobile). It reads the page you're on and can click, type, navigate and fill in forms itself, using the logins already sitting in your browser. There's no separate credential to hand over and no scraping code to write — it sees the page exactly as you'd see it, because it's acting inside your own session.
The workflow: record it once, let it run itself weekly
- Open the extension's side panel and click Start Recording.
- Do the task exactly as you always do it — log in, click through, download the report. Claude watches and records each step.
- Click Stop Recording. That sequence is now a saved shortcut you can re-run or hand to someone else.
- Click the clock icon, turn on Schedule, and pick a cadence — daily, weekly, monthly or yearly — plus a time and which model runs it.
Log into the supplier portal, open Orders > This Week,
download the CSV, and rename it with today's date. Runs
every Monday at 9am.One thing to know going in: this needs your computer on and Chrome open at the scheduled time. It isn't a cloud job running while your laptop's shut — if the machine's asleep, the task waits for the next time both are on. Schedule it inside hours you know the machine will actually be up, not for 2am if you close your laptop every night.
What it won't do without asking, and what it won't do at all
Per site, you choose between approving one action at a time or letting Claude act on that site without asking. Even on a site set to run unsupervised, it still stops to ask before a download, before entering anything sensitive, and before granting any authorization. Some actions are blocked outright, on every plan, regardless of what you've set: Claude in Chrome will not make a purchase, create an account, bypass a bot check, execute a trade, or permanently delete something. Those aren't settings you can turn on — they're refused by design.
Read the recording before you trust it
A malicious page can hide instructions in its own content — invisible text, a fake pop-up — trying to redirect what Claude does next. Anthropic trains against this and scans page content for it, but the simplest defence is yours: watch the first few scheduled runs of a new shortcut before switching that site to always-allow, especially anywhere the portal touches money or personal data.
What it actually replaces
Not an API — there still isn't one, and the shortcut is exactly as fragile to a redesigned portal as you clicking through it yourself would be. What it replaces is the person who has to remember it's Monday, and the version of the numbers that gets mistyped when that person is doing it half-awake before their first coffee. The chore was never worth an engineer's time. Now it doesn't need to be.
This was never going to get an integration budget. It just needed someone to stop being the one clicking through it.
Where it's the wrong tool
- Anything that ends in a purchase, a new account, or something irreversible — it's refused outright for the first two, and worth a human's eyes on the submit step for anything else with real consequences.
- A portal behind a CAPTCHA or heavy bot detection will interrupt the run and need a person anyway.
- A task your machine won't be awake for — it needs Chrome open on a running computer at the scheduled time, not a laptop that's shut for the night.
- Real volume. This is built for one click-through a week, not thousands of records — that's a genuine integration project, or [batch processing](/blog/batch-your-ai-calls-halve-the-bill) if there's a model call involved.
None of this makes the portal any less badly built. It just means the badly built portal stops being your Monday morning.
Working out which of your team's manual, no-API chores are worth handing over this way — and which ones actually need a real integration — is exactly the kind of call we help make in an AI consultation.