Most people only ever use the chat box, so their mental model of AI is "it tells me things". Claude in Chrome is a different shape. It is a browser extension that reads, clicks and navigates websites alongside you, inside your real browser, in your real logged-in tabs (official getting-started article). That last detail is the whole point: it works inside the accounts you are already signed into, so it never hits a login wall on the tools you actually use.
The admin that has been on your list for a month usually survives because it is thirty small decisions, none of them hard, spread across six tabs. That is exactly the shape of task worth handing over.
debugger, which is what actually lets Claude click buttons, type text and take screenshots. Every permission and the reason for it is documented in the getting-started article, and it is worth reading once rather than clicking through.There is a drop-down on the chat input with three modes, and picking the right one is most of the safety story. From Anthropic's Claude in Chrome permissions guide:
The first task decides whether you ever use this again. A good candidate is boring, repetitive, has a clear finished state, and does not need your taste in the middle of it.
The classic month-old task. Describe the outcome, not the clicks, and give it the source of truth to work from.
I have [the page, for example "my profile on this marketplace" or "my media kit page"] open in this tab and it is out of date. Bring it up to date for me. Work through the page section by section rather than fixing one field and stopping.
Here is the current, correct information to use, and do not use anything else, do not round numbers up, and do not invent a credential, a client, a follower count or a date that is not in this list: [paste your real current stats, bio, links, services, rates, locations and anything else the page asks for].
Go through every editable field on the page, including the ones collapsed behind "edit" or "show more" or a second tab, and update anything that no longer matches the list above. Where a field asks for free text like a bio or description, rewrite it in the same voice as the text I gave you rather than making it more formal. If a field asks for something that is not in my list, stop and ask me instead of guessing.
Before you save anything, show me a plain list of every change you are about to make, in the format "field: old value becomes new value", and wait for me to confirm. Do not delete an existing section to make room for a new one, do not change my username or my email, and do not touch anything to do with payments or account settings.Drag the relevant tabs into Claude's tab group first. Claude can view and interact with every tab in that group at once, so you stop hopping between them.
I have grouped several tabs for you. Go through every tab in your tab group and pull them into one comparison table for me. Do not change, submit, send or delete anything on any of these pages: this is a read-only job.
For each tab, record these fields: [list exactly what you need, for example the name, the price, the plan or tier, the renewal date, the cancellation link, and the account the subscription is billed to]. Where a field genuinely is not on the page, write "not shown" rather than leaving it blank or guessing a plausible value, because a blank cell and a missing value look identical later and I will not be able to tell them apart.
Give me the result as a table I can paste straight into a spreadsheet, one row per tab, sorted by [the field that matters, for example cost, highest first]. Under the table, tell me how many tabs you covered so I know none were skipped, and flag anything that looked unusual, for example a plan I appear to be paying for twice or a renewal inside the next seven days.
If a page will not load, sits behind a login, or shows something different from what I described, stop and tell me which tab and what you saw instead of working around it.Long application forms, directory listings, supplier onboarding, insurance renewals. The instruction that makes this safe is the hard stop at the end.
Fill in the form on this page for me using the details below, and stop before submitting it. Do not click submit, send, apply, pay or confirm under any circumstances, even if the form warns me that progress will be lost.
My details: [paste name, business name, ABN or registration number, address, email, phone, website, and anything else the form is asking for]. For the longer free-text questions, here is what I want to say and the tone I want: [paste your notes, or a previous answer you were happy with].
Work through the form in order, including any steps hidden behind "next" or "continue", and expand every conditional section that applies to me. For any question you cannot answer from my details, leave it empty and add it to a list rather than filling it with something plausible. For any question where two of my answers could both be correct, pick the more conservative one and tell me you did.
When you reach the final review or submit screen, stop there and give me two things: a list of every field you filled with the value you entered, and a list of every field you left for me. Then wait. I will read it and press submit myself.Matching invoices to transactions, receipts to a spreadsheet, orders to bookings. Claude has built-in knowledge of how to navigate common platforms including Gmail, Google Calendar, Google Docs, Slack and GitHub, so this kind of cross-checking is one of the things it handles most reliably.
I need two systems reconciled and I want a report, not action. Read-only: do not send, reply, forward, delete, archive, mark as read, upload or attach anything anywhere.
System one is [for example my email inbox, searched for invoices and receipts between these dates]. System two is [for example the transactions or expenses list in this accounting tool, same date range]. Go through system one item by item and try to find the matching entry in system two, matching on amount first, then date within a few days, then the supplier or sender name.
Give me four clearly separated lists. Matched: the items you found in both, with the amount, the date and the supplier. In system one only: things I have a receipt for that are not recorded, which is usually what I am missing. In system two only: recorded items with no receipt attached. Uncertain: anything where you found a near-match but the amount or the date does not line up, with both values shown so I can judge it myself.
Do not merge an uncertain match into the matched list to make the numbers tidier, and give me a count for each list at the top. If you run out of items to check or hit a limit on how far back you can search, say exactly where you stopped.The prompts above are long on purpose. The good news is that you write them once. When one works, keep it.
/ in the chat and picking it, instead of rewriting the instruction each time.Two more things worth knowing before you build a week around this. Agentic browsing is a multi-minute activity, not a two-second one, so it buys back your attention rather than raw clock time: start it and go do something else. And Claude cannot tell that the underlying information was wrong, so a run that executes perfectly on bad source data gives you confident, wrong output. The review step at the end is the part you keep.
Anthropic is explicit that this is a genuinely risky capability and worth reading up on before you use it heavily. Their guidance is in use Claude in Chrome safely, and if the extension misbehaves there is a troubleshooting article.