What changed
Claude Code on desktop shipped a built-in browser in Week 28 (July 6-10, 2026), versions v2.1.202-v2.1.206 1. Claude can pull up docs, designs, issue trackers, internal web apps, or virtually any other site, then read page contents, click links, and interact with elements the same way it already drives your local dev-server previews 13. The load-bearing detail is not that it browses, it is how: the Browser pane runs a clean, isolated profile with none of your saved logins or history, it is sandboxed, and you choose whether sessions persist 23. This is a shipped Desktop feature that is live now, not a preview.
The two surfaces
One week earlier, in Week 27 (June 29-July 3, 2026), Anthropic made “Claude in Chrome” generally available, and that extension drives your real Chrome with your real sessions 1. So there are now two browser surfaces with different trust models, and the interesting fact is the split, not either feature alone: you pick the browser by whether the task should see your authenticated identity.
| Surface | Identity / logins | Best for |
|---|---|---|
| Claude in Chrome extension | Your real Chrome, your real sessions | Tasks needing authenticated access 2 |
| In-app browser (Desktop) | Clean, isolated profile, no saved logins | Build-and-verify, sites that don’t need your identity 2 |
The so-what: the in-app browser closes the build-and-verify loop (open the docs, drive the running app, read the issue tracker) without ever handing an autonomous agent your production cookies, so the safe default for build-and-verify work is now the identity-free surface.
Impact on your team
When you wire an agent to a browser, the decision that changed is which surface. Default your build-and-verify work to the identity-free in-app browser on Desktop, and reserve the Chrome extension for the authenticated paths: login-gated end-to-end tests, anything that needs your real session 2. The concrete move is to adopt the in-app browser now for docs, dev-server, and issue-tracker loops, keep the extension for authenticated flows, and never point an autonomous, click-happy agent at your live cookies when the task does not need them.