Claude Code can now work directly with external websites through a built-in browser window. Anthropic added the feature so Claude can open web pages, read them, click through them and type into them from inside the app.
The change gives Claude Code a more direct way to use online resources during a coding workflow. Instead of only relying on local context or a user copying information into the app, Claude can interact with pages such as documentation sites, issue trackers and similar resources.
What Claude Code can do in the browser
The new browser works like a tab-based browser inside Claude Code. It opens with a keyboard shortcut and gives Claude a way to move through web pages while staying inside the app.
According to the source article, Claude can now perform several basic browser actions on external websites:
- Open web pages
- Read page content
- Click links and interface elements
- Type into web pages
Those abilities matter because many coding tasks depend on information that lives outside a local project. Documentation sites explain APIs and libraries. Issue trackers hold bug reports, project discussions and implementation details. Similar resources can help an assistant understand what a user is trying to build or fix.
The browser does not appear as a separate product in the source article. It is presented as an integrated Claude Code capability, meaning the web interaction happens inside the same environment where the assistant is already helping with code-related work.
Why this changes the workflow
Claude Code already had tools for previewing local apps. The new browser uses the same tools, but applies them to external web pages with additional safety checks.
That distinction is important. Previewing a local app is different from acting on an external website. A local preview usually sits within a user’s development environment. An external website can involve forms, buttons, account flows or actions that affect services beyond the local machine.
By adding browser access, Anthropic is giving Claude Code a more practical way to gather and use information from the web during development. A user working through a coding problem may need Claude to inspect documentation, compare behavior against an issue tracker or understand how a web resource is structured.
In plain terms, the feature reduces the need for manual copy-and-paste between a browser and Claude Code. Claude can look at the relevant page directly, then use that information while continuing the coding session.
The safety limits are part of the feature
The source article emphasizes that Anthropic added extra safety checks around the browser. Claude uses classifiers to screen write actions on external sites.
Write actions are more sensitive than reading a page. Reading documentation is low-risk compared with typing into a form, pressing a button or attempting an action that could change something on a website.
Claude also will not buy anything, create accounts or bypass CAPTCHAs without user consent. These limits keep the browser from becoming an unrestricted automation tool for external services.
The browser runs on a clean profile with no saved logins. That means Claude is not automatically operating inside a user’s existing signed-in web sessions through this built-in browser.
This design creates a clear boundary. Claude Code can use the web for research and interaction, but the built-in browser does not inherit saved accounts or stored sessions from a user’s normal browser profile.
Controls for organizations
Anthropic also gives organizations ways to limit the feature. Organizations can restrict access to external sites through an allowlist or disable the browser tools entirely.
An allowlist gives an organization a way to define where Claude Code may browse. Disabling the browser tools entirely gives a stricter option for teams that do not want external site interaction inside Claude Code.
These controls are relevant because teams may have different policies for development tools, external websites and automated actions. Some may want Claude to read approved documentation sources. Others may prefer to keep all browsing outside the coding assistant.
The source article says Anthropic announced these organization controls on X. It also notes a separate path for users who want Claude to act within their own logged-in sessions.
When to use the Chrome extension instead
The built-in Claude Code browser uses a clean profile with no saved logins. For users who want Claude to act within their own logged-in sessions, the source article says they should use the Chrome extension instead.
That creates a practical split between two use cases. The integrated browser is for working with external websites from inside Claude Code without saved logins. The Chrome extension is the option named for cases where Claude needs to operate in the user’s own logged-in browser context.
For developers and organizations, the main takeaway is straightforward: Claude Code now has a browser for external web pages, but Anthropic has paired that access with consent requirements, classifier checks, clean-session behavior and administrative controls.