[FEATURE] Build Chrome Replacement

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Anthropic-built browser to eliminate Chrome dependency for web automation

Proposed Solution

Summary
Claude Code's browser automation is entirely dependent on Chrome via an MCP extension. This creates a fragile, unreliable foundation that Google can break at any time. Anthropic should build or bundle its own browser/webview purpose-built for AI-assisted web automation.

Problem
A quick search of this repo tells the story — dozens of open issues about the Chrome extension not connecting (#45230, #40758, #37541, #35675, #41879, #37027). This isn't a bug to fix; it's an architectural dependency on a platform Anthropic doesn't control.

Specific risks:

Manifest V3 restrictions — Google is actively limiting what extensions can do, and further lockdowns are expected
Extension policy changes — Google can delist or restrict the Claude in Chrome extension at any time
Anti-automation design — Chrome is built for human users, not AI agents. Every automation capability is a workaround, not a supported use case
Connection fragility — Native messaging, tab groups, and extension lifecycle are all failure points that generate constant support burden
Proposal
Anthropic already ships a desktop app. Bundle a lightweight browser engine (Chromium-based webview or similar) that:

Connects natively to Claude Code without an extension layer
Provides first-class automation APIs instead of screen-scraping workarounds
Can't be broken by Google policy changes
Handles auth, cookies, and sessions in a way designed for AI-assisted workflows
This doesn't need to replace Chrome for general browsing — just for the automation use cases Claude Code needs.

Why this matters
Browser automation is one of Claude Code's most powerful capabilities, but it's also the most fragile. Every user who hits a "browser extension not connected" error loses trust in the platform. Owning the browser layer turns a liability into a competitive advantage.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

MCP server integration

Use Case Example

_No response_

Additional Context

_No response_