OpenClaw 3.13 supports Chrome 146 via MCP for signed-in browser control
OpenClaw 3.13 now connects to a real Chrome 146 session over MCP so agents can drive your signed-in browser instead of a separate bot context. Update if captchas or auth state were blocking your web automation flows.
TL;DR
- OpenClaw 3.13 now connects to Chrome 146 over MCP, and the launch post says the agent can control "your real browser session" instead of a separate bot browser.
- The practical pitch is fewer auth and anti-bot blockers: Ray Fernando's post leads with "No more captchas," tying the update directly to signed-in browsing.
- Setup appears aimed at local desktop use first, with the announcement calling Mac and PC the "easiest config" and the follow-up post pushing users to update if they have not yet.
- The broader developer takeaway is browser access through the browser you already use: in Addy Osmani's repost, Chrome is described as making a "real, signed-in browser" accessible to coding agents.
What shipped
OpenClaw 3.13 adds Chrome 146 support via MCP. In the primary announcement, Ray Fernando says the new path lets an agent drive "your real browser session" and stresses "Not a bot. You." That is the key implementation change: the agent is no longer framed as operating in an isolated automation context, but through the users existing signed-in Chrome session.
The same post ties the release to a specific pain point by opening with "No more captchas." A follow-up post keeps the message simple update to 3.13 if browser automation has been blocked by current auth state or anti-bot checks. The attached demo video setup demo shows a terminal-based connection flow ending in a successful OpenClaw interface connection.
Why it matters for agent workflows
For engineers building browser agents, the notable part is not just another web automation connector. The supporting repost summarizes the change as access to a "real, signed-in browser," which implies existing cookies, sessions, and account state can stay in the loop when an agent acts through Chrome.
That matters because many brittle flows happen after login: internal tools, purchasing portals, dashboards, and consumer sites that aggressively challenge fresh automation contexts. OpenClaw's launch language explicitly positions 3.13 against that failure mode, and its setup note narrows the current sweet spot to Mac or PC desktop environments rather than a generic hosted runtime.