Claude built-in browser or Chrome: choosing for your workflow

Two routes with different starting points

The built-in browser opens web tasks inside Claude Desktop. The announcement covers Pro, Max and Team, with administrative enablement for Enterprise; Linux remains in beta. The desktop app must be open and online for this browser, including when controlled from a phone. Individual sign-ins can be deliberately transferred without broadly sharing the user’s browser.

Claude in Chrome became generally available on all paid plans in the same release. The extension works with open pages and existing sign-ins. The choice therefore depends on whether you are delegating a separate web task or continuing work on a page already open. September’s unified Claude interface does not automatically remove local execution dependencies.

Example: collect documents from a supplier portal

A bounded built-in-browser assignment could collect approved monthly documents from a supplier portal. Specify the supplier, period, document type and destination folder. Ask first for a list of available documents and missing months. An invoice and a credit note should not be treated as equivalent simply because their filenames look similar.

After download, a responsible person checks completeness, invoice numbers and amounts against the portal’s overview. Counting downloaded files is insufficient. Specify that the task must not change payment details or mark invoices as paid. This turns an open-ended request to “handle the bookkeeping” into a verifiable preparation task.

Example: work with a page already open

Chrome may fit when the responsible person is already working in the correct customer account and record. An initial task could summarize an open project dashboard and draft notes for the next meeting. Confirm the project identity and visible reporting period before using the information. Similarly named browser tabs do not establish an unambiguous business context.

For later form entry, first request a draft showing every field to change. Review the values, apply the appropriate change set and then check the saved state. A documented human acceptance step matters more than typing speed, particularly in portals without a clear change history.

Understand autonomous actions and untrusted page content

Anthropic describes safeguards against hidden instructions in web pages and checks on planned actions. It also states that the risk cannot be eliminated. A page, email or document may contain content intended to divert the agent from the original task. Such content is task data, not a new authorization.

For an initial business pilot, we recommend familiar sites, limited account permissions and a short list of allowed actions. Orders, sending, publishing and deletion should have their own approval points. An account switch or unexpected sign-in page is a reason to stop. A person should verify the context before the agent continues with broader access.

Test interruptions and completion evidence

Test a normal run, an expired sign-in and a desktop interruption. The team must distinguish completed work from partial completion or a mere announcement. Restarting should not create the same record twice or resend a message. For recurring use, include these cases in a short operating procedure.

Also compare browser control with existing exports or documented interfaces. A stable data connection may better suit the same assignment. Browser interaction is particularly useful when a required interface has no suitable alternative access. The decision should depend on verified results and manageable effort rather than maximizing the number of automated clicks.

A concise completion note should name the sources opened, files actually created, outstanding steps and known exceptions. A colleague can then take over without guessing from the conversation which actions have already happened.

Common questions about Claude in the browser

Does the built-in browser keep working without the desktop? The documented implementation requires the desktop app to remain open and connected. Is Chrome always preferable? No; the particular page, sign-in and task determine the fit.

Are browser actions automatically safe? Vendor checks reduce risks but do not replace suitable permissions and acceptance checks. Where should we start? Choose a small task with a known expected result. The AI System Check helps assess whether browser control, a connector or an existing export fits best.