chrome-use lets Claude Code and Codex drive a signed-in Chrome

On October 27, 2026, the AI section of DEV Community ran a writeup introducing chrome-use, an open-source (Apache-2.0) CLI and MCP server that lets Claude Code, Codex, Cursor, or your own scripts drive the Chrome browser you already have signed into, rather than requiring a separate debug port or a freshly launched automation browser.

The post frames the problem it addresses as a common stuck point: when you ask a coding agent to "check the open issues on our dashboard," it usually fails at the first step. The browser such an agent drives is a clean automation browser signed in to nothing, while your cookies, your SSO session, and your 2FA-protected accounts all live in the Chrome window you already have open, not in the one the agent just launched.

chrome-use is presented as the answer to that gap. As a CLI and MCP server, it gives agents direct access to account pages protected by cookies, SSO sessions, and 2FA. The writeup describes how it works and how to hook it up to Claude Code, Codex, Cursor, or custom scripts, but it does not go deeper into implementation details. No performance numbers, benchmarks, or other metrics are cited, and no company or individual is credited as the author or maintainer of chrome-use beyond the DEV Community post itself. The current state of the record is therefore limited to that single feature introduction: chrome-use exists, it is Apache-2.0 licensed, it runs as a CLI and MCP server, and it targets signed-in Chrome sessions for agentic browser use.