How to Use Claude in Chrome to Write Directly to a Web App

Q: Is there a risk of Claude submitting forms I don't want submitted?

Yes, if the work order includes a submit step. Always review work orders that include submit, confirm, send, or delete actions before execution.

Q: What if the UI changes and Claude can't find an element?

Claude in Chrome will report it couldn't find the element and stop. It will not guess or click something else.

The Pattern
Claude Chat writes the work order. Claude in Chrome navigates the UI and executes it. This combination lets you automate web apps that have no API — or where the API doesn’t expose what you need.

A lot of the most useful tools on the web don’t have APIs. Or they have APIs, but specific features — a particular button, a workflow trigger, a UI-only setting — aren’t exposed through them. For years, the workaround was Zapier, custom scripts, or doing it manually.

Claude in Chrome opens a different path: Claude navigates the UI directly, the same way you would, but you don’t have to be the one clicking.

How the Two-Claude Pattern Works

The workflow that works well in practice uses two Claude instances working together:

Claude Chat (the claude.ai interface) handles planning, writing, API calls, and generating the specific instructions for what needs to happen in the browser
Claude in Chrome (the browser extension) receives those instructions and executes them directly in the web app UI

The typical flow: you describe the task to Claude Chat. Claude Chat writes a precise, step-by-step work order — what page to navigate to, what to click, what to fill in, what to confirm. You paste that into Claude in Chrome. Claude in Chrome executes it in the browser.

It’s not magic. It’s division of labor: reasoning on one side, execution on the other.

Real Situations Where This Applies

In documented use, the Claude Chat → Chrome pattern has been used for:

Cloud console navigation — walking through multi-step infrastructure setup in a browser-based cloud console where the relevant actions weren’t exposed through the provider’s CLI or API
Domain registrar settings — updating DNS records through a registrar’s web interface. The registrar had an API, but the specific record type needed wasn’t in it.
Social scheduling tools — posting or scheduling content through a platform’s web UI when the API tier available didn’t include the scheduling endpoint
Web-based terminal environments — operating Cloud Shell or browser-based terminals without switching windows or copy-pasting
Browser-based AI notebook tools — creating notebooks, adding source URLs, navigating to generation features, and triggering video or audio generation through a UI

The common thread: a logged-in browser session was required, and the action wasn’t available through an API.

⚠️ Pre-login before you hand off. Claude in Chrome can only interact with services where you’re already logged in in that Chrome profile. If Claude navigates to a page that requires a login it doesn’t have, it will stall or hit an error. Log in to every service you intend to use before starting the session, and make sure the session hasn’t expired. Also: close any tabs with services you don’t want Claude to interact with during this task.

What Makes a Good Work Order

The quality of the Chrome execution depends heavily on the quality of the instructions Claude Chat produces. A good work order is:

Sequential. Each step follows the last. Claude in Chrome doesn’t skip around.
Specific about UI elements. “Click the blue Save button in the upper right” is better than “save it.”
Includes what to do if something unexpected appears. Login screen, confirmation dialog, error message — Claude in Chrome handles these better if the work order anticipates them.
Ends with a confirmation step. “After completing, read the page and report what you see” closes the loop so you know whether the task actually finished.

Claude Chat is good at generating this kind of structured instruction when you describe the task well. Give it the context of what tool you’re working in, what you’re trying to accomplish, and what you expect the UI to look like.

The API-First Rule

Using Claude in Chrome to operate a web UI is slower and less reliable than using an API. UI layouts change. Buttons get renamed. A platform update can break a workflow that worked yesterday.

The rule that holds up in practice: API first, Chrome when the API fails or doesn’t exist.

If a tool you use regularly exposes the action you need through an API, build the API integration and use that. Chrome UI automation is the fallback — valuable and often the only option, but a fallback nonetheless. Don’t default to Chrome just because it’s faster to set up today.

⚠️ Don’t leave Claude in Chrome running on high-stakes UI actions without reviewing first. If your work order includes steps like submitting a payment form, publishing content publicly, deleting records, or sending a message — review the work order carefully before Claude executes it, and stay present during execution. UI actions in Claude in Chrome are real. There is no undo button built in.

When the Work Order Approach Doesn’t Work Well

A few situations where the Claude Chat → Chrome hand-off runs into friction:

Dynamic UIs with inconsistent layouts. If the UI renders differently based on account state, screen size, or A/B tests, Chrome may not find the element the work order described.
Multi-factor authentication prompts. If a service triggers MFA mid-session, Chrome will stall waiting for input. You need to be present to handle it.
Very long multi-step tasks. The longer the chain of actions, the more likely something unexpected will interrupt it. For long tasks, build in manual check points rather than treating the whole thing as one uninterrupted run.
Anything involving CAPTCHA. Chrome cannot solve CAPTCHAs. Tasks that require CAPTCHA completion need manual intervention at that step.

Frequently Asked Questions

Does Claude in Chrome work with any website?

It works with any website loaded in Chrome where you have the appropriate access. The extension interacts with the live DOM of whatever page is open. Some sites use security measures that prevent external scripts from interacting with certain elements, which can limit what Claude can click or read on those pages.

Can Claude in Chrome interact with pop-up windows or modal dialogs?

Yes, in most cases. Pop-ups and modals that are part of the page’s DOM are accessible. Browser-level dialogs (like the native file picker or browser alert boxes) have more limited interaction.

What if the UI changes and Claude can’t find an element?

Claude in Chrome will report that it couldn’t find the element and stop. It won’t guess or click something random. You’ll need to update the work order to reflect the current UI, or manually navigate to the right state and then reconnect.

Is there a risk of Claude submitting forms I don’t want submitted?

Yes, if the work order includes a form submission step. Always review work orders that include submit, confirm, send, or delete actions before execution. If you’re uncertain, break the work order into stages and review what Claude has done before authorizing the next stage.

Can I use Claude in Chrome for a tool I use for work with sensitive data?

Use judgment. Claude in Chrome processes what it sees in the browser tab, and the content of that interaction is processed by Anthropic’s systems under your account’s privacy settings. Review Anthropic’s privacy policy for your plan before using Claude in Chrome with tools containing confidential, regulated, or personally identifiable information.