Which Claude plan includes the Chrome extension?

Pro and above as of 2026. Free accounts don't see the 'Claude in Chrome' option in settings. If you're on Free and want to try it, the Pro plan at $20/month is the lowest tier that unlocks the extension plus scheduled tasks.

Will this work on Safari or Firefox?

Officially, Chrome and Chromium-based browsers only. Edge, Arc, and Brave mostly work because they share the Chromium extension architecture. Safari and Firefox are not supported — the extension APIs are different enough that there's no equivalent build.

Can Claude handle websites that require login?

Yes, as long as you're already signed in when the task runs. Claude uses your existing browser session. The edge case: sessions that expire between scheduled runs — a weekly task hitting a site that logs you out after seven days will fail silently.

What happens if a CAPTCHA appears?

The extension respects bot-detection systems. Claude won't try to solve CAPTCHAs or bypass human-verification walls. If your target site aggressively gates with Cloudflare or hCaptcha, you'll need to pick a different source or run the task manually through the step.

Does the scheduled task need my laptop to be open?

Yes, unless your plan includes cloud-hosted scheduled browsing. Local scheduled tasks need Chrome running on a machine with the extension signed in. Teams often dedicate an always-on mini PC or a cloud VM for this; individuals just make sure the laptop's awake at the scheduled time.

How Do I Install Claude in Chrome and Schedule a Recurring Browser Task?

The Claude Chrome extension is the difference between "Claude can draft stuff" and "Claude can actually run my browser for me." Once it's installed and a workflow is scheduled, you get an assistant that opens tabs, reads pages, fills forms, and reports back on a cadence you choose — instead of you remembering to do the same 14-step research routine every Monday. This guide gets the extension set up and your first recurring browser task running end-to-end.

Why this matters

Most "AI in the browser" tools are a chat sidebar that can see the page you're on. Useful, but still manual — you're the one driving the tabs. The Claude Chrome extension plus Claude's scheduled tasks change the shape: Claude can drive Chrome itself (navigate, click, read, type) and a scheduled task fires the whole workflow without you opening it.

The killer use case: anything you do every week that starts with "open five tabs and check…" becomes a single recurring task. Competitor price checks, Google Search Console pulls, LinkedIn prospecting lists, status-page monitoring, ad-creative scraping — all on a cron, landing as a report in your email or Slack.

Before you start

You need:

Chrome (or a Chromium browser — Edge, Arc, Brave mostly work, but official support is Chrome).
A Claude.ai account with access to Claude in Chrome. As of 2026, it's rolled out to Pro and above. If you don't see the "Claude in Chrome" option in your Claude settings, you're probably on Free.
A target workflow in mind. Don't install the extension in the abstract — pick one thing you'd run weekly. We'll build that. "Pull top 5 SERP results for my 10 tracked keywords and summarize any movement" is my usual first one.

Step 1: Install the Chrome extension

Go to claude.ai → Settings → Claude in Chrome (or whatever it's named in your version — may be "Browser agent" or "Claude for Chrome"). Click Install extension.

Chrome will prompt you for permissions. The extension needs:

Read and change all your data on websites you visit — scary-sounding but necessary. This is how it sees the page.
Manage your tabs — to open new ones, switch, close.

Approve. Pin the extension to your toolbar (puzzle icon → pin Claude) so you can find it.

Step 2: Authenticate the extension

Click the extension icon. It opens a side panel in Chrome and asks you to sign in with your Claude.ai account. Sign in.

You'll know it's working when the side panel says something like "Claude is watching this tab" with your current URL.

Quick sanity check: open any article, open the Claude side panel, and ask "summarize this page." If you get a summary, the extension is reading the page correctly and you're authenticated.

Step 3: Give it a task and let it drive

This is the part that's different from every "AI sidebar" product. In the side panel, type something that requires action, not just reading:

"Open Google, search for 'best ergonomic office chair 2026 under $500,' open the top 3 results in tabs, and give me a one-paragraph summary of each with price."

Hit enter. Claude will:

Ask for confirmation that it can navigate on your behalf (first time only).
Open a new tab, go to Google, type the query, hit search.
Click the first result, read it, come back, click the second, etc.
Report back in the side panel.

Watch it work. The first few runs feel uncanny — like watching someone use your computer. You'll want to stop it and take over. Resist the urge; let it finish. It'll do a worse job than you would, and that's fine — you're building trust in what it can and can't do.

Step 4: Turn the task into a scheduled job

Once a task runs cleanly once, save it as a scheduled task so you never have to trigger it manually.

In the Claude side panel, hit the … menu → Schedule this task (or "Make recurring"). You'll see:

Frequency: daily / weekly / custom cron.
Delivery: email, Slack, or just keep results in Claude.
Prompt: prefilled from what you just ran. Edit it for recurrence-friendliness (e.g., instead of "this week's numbers" say "numbers for the current ISO week").

For the SEO example, I run: "Every Monday at 7am, open Google Search Console, pull the last 7 days of performance for my 10 tracked queries, note any that dropped more than 2 positions, and email me the list."

Save it.

Step 5: Test the scheduled run

Don't wait until next Monday to find out it's broken. Most schedulers have a Run now button. Hit it. Read the output. Fix the prompt if needed. Re-run.

A scheduled browser task is only as reliable as its prompt. Ambiguity that's harmless in a one-off chat ("look for my tracked keywords") will fail silently on a schedule because there's no one in the room to notice. Be specific: "the 10 keywords listed in this document" (paste them in), "positions 1–10 only," "email me even if nothing changed, so I know it ran."

Verify it worked

Three checks.

1. Extension icon is green/active. If it's grey, you're not signed in or permissions are missing.

2. A run that you can point at. Task history in Claude should show your test run with a timestamp and the report output.

3. Email or Slack actually delivered. If you chose a delivery channel, confirm the message arrived. Claude occasionally silently fails delivery if the destination email has aggressive spam filtering.

Where this breaks

Sites with aggressive bot detection. Cloudflare challenges, hCaptcha walls, and LinkedIn's login gate will stop Claude cold. The extension respects those — it won't try to solve them. Pick tasks on sites that don't gate.
Logged-in sessions that expire mid-task. If the target site logs you out after 24 hours, a weekly scheduled task running at 3am on day 8 is going to hit a login screen and fail. Fix: pick sites where you stay signed in, or use tasks that don't require auth.
Two-factor authentication. If the flow triggers 2FA, Claude can't complete it. Workaround: do the 2FA-requiring part manually and have Claude pick up from there, or use app-specific passwords where possible.
The "runs in the background" assumption. Scheduled browser tasks need Chrome to be running on some machine. If you close your laptop for the weekend, a Saturday morning run won't fire. For truly hands-off, use a dedicated always-on machine or the cloud-hosted option if your plan includes it.
Prompt drift. A task that worked in January may break in April because the target site redesigned. Re-verify your critical scheduled tasks monthly.

What to try next

How Do I Schedule Claude Code to Run Overnight Jobs? — the CLI-side equivalent for non-browser work.
How Do I Use Claude's New Memory Feature Without Leaking Client Data? — critical if you're giving the Chrome extension access while logged into client accounts.
How Do I Set Up a Claude MCP SEO Stack? — if your recurring task is SEO-focused, MCP connects to Google Search Console directly without needing the browser at all.