Getting Started

chrome-use

chrome-use lets any AI agent drive your real, logged-in Chrome — Claude Code, Cursor, Codex, your own scripts. It reuses your existing login sessions and browser profile. Detector results are documented for the tested conditions: CreepJS scores it 0% bot.

bash

# install the CLI — no npm, no tokens
$ curl -fsSL https://raw.githubusercontent.com/leeguooooo/chrome-use/main/install.sh | sh

✅ New here?

Read Install & Setup to connect the browser extension, then walk the Core Loop (snapshot → find → act) — that's 90% of everything you'll do with chrome-use.

Why chrome-use

Connect an agent to the Chrome profile you already use. You keep the existing login sessions, watch its work and take over when a website requests verification. Fresh browser contexts start without those sessions; other automation tools can also use persistent profiles or existing-browser connections, so compare the actual connection path.

🔒 Your real, logged-in Chrome

Your cookies, sessions, and fingerprint are all real — because it IS your real browser. See the detector measurements and their limitations.

🧩 Extension, not a debug port

A one-click Store extension over native messaging — no --remote-debugging-port, so it never pops "Allow remote debugging?".

🎨 Multi-agent isolation

Each --session gets its own colored tab group, so many agents share one real Chrome without stepping on each other.

🕵️ Silent operation

Runs entirely in the background — new tabs open un-focused, the agent never force-fronts a tab or steals your foreground.

Why not just use…

Playwright / Puppeteer / browser-use? A new browser context starts without your existing sessions. Those tools can also use persistent contexts or existing browsers; compare connection setup and ownership for your workflow. chrome-use uses the session you already have.
Claude's Chrome extension? Great, but it only drives Claude. chrome-use drives any agent or CLI over the same real browser.
A raw --remote-debugging-port? Chrome 136 restricts debugging of the default profile; connection requirements vary by Chrome version and mode. chrome-use never does — one-click Store extension, native messaging.

ℹ️ The receipts

Real-browser fingerprint verified against the toughest public detectors: CreepJS 0% stealth · 0% headless, no Runtime.enable CDP leak (off by default), and a small permission footprint — 12 permissions, no <all_urls>. See Real Chrome & Anti-detection.

What detector results mean

The documented CreepJS run reported 0% bot and 0% headless. This is a measurement in a particular environment, not a promise of invisibility or account safety. Websites can also evaluate behavior, account history and network signals. Read the test conditions; hand login challenges to the user.

🛡️ CreepJS 0% bot · 0% headless

When it drives your real Chrome over the extension it injects no JS patches — no disguise means no seams for the lie-detectors to catch. bot.incolumitas / sannysoft / BrowserScan all green.

⚙️ Native overrides > JS lies

The --launch standalone browser uses native overrides: navigator.webdriver=false (Emulation.setAutomationOverride), timezone, WebRTC local IP, canvas/audio noise — none of them redefined getters that can be probed back. Headless is disabled by default (it's a bot tell in itself).

🖐️ --humanize beats behavioral detection

Beyond fingerprints, Akamai / PerimeterX / DataDome also score behavior. Turn it on and the cursor follows curved Bézier paths, lands on jittered points inside the element, and typing cadence varies — and it's adaptive: it escalates on pages from those vendors, and stays instant with zero overhead on ordinary sites.

☁️ Cloudflare pass-once, reuse

The cf_clearance earned by clearing a challenge once (bound to IP+UA) is saved and reused, so you don't re-solve it every time. Run chrome-use stealth status anytime to self-check the webdriver / chrome / plugins / UA probes.

Stealth & Anti-detection →

Get started

A few short reads take you from zero to driving your own Chrome:

📦 Install & Setup

One-line installer, then the browser extension + native-messaging bridge.

🔁 Core Loop

snapshot → find → act: the read/interact rhythm behind every task.

📖 Reading Pages

Pull a structured, agent-friendly view of any page with snapshot.

🔌 MCP Server

For hosts that can't shell out — Claude Desktop, ChatGPT connectors — via chrome-use mcp.

The *-use family

Same idea across the board: don't build a simulated environment — drive the real, already-logged-in device you're holding.

🌐 chrome-use

Drives your real, logged-in Chrome.

📱 iphone-use

Drives your real iPhone.

🔑 bitwarden-use

Pulls passwords, 2FA, and passkeys from your Bitwarden vault so an agent can log in with credentials.

Apache-2.0 · GitHub · part of the leeguoo.com *-use family.

Originally based on vercel-labs/agent-browser (Apache-2.0), now standalone · Lineage & Upstream · Privacy