// Reference

The *-use Family

chrome-use is just one piece of a bigger idea. The whole *-use family shares the same philosophy: no simulated environments, no virtual machines, no fingerprint spoofing — take over the one real, already-logged-in device in your hand. Browser, phone, password vault, account sessions — each is an open-source tool an agent can safely call.

One idea: drive real devices

Simulated environments always have cracks: a brand-new browser fingerprint, a session with no login state, automation traces that anti-bot systems can spot. Every tool in the family flips the premise: it is the device you were already using, so cookies, sessions, login state, and fingerprint are all naturally real. The agent is just pressing buttons for you.

✅ What they share

Every tool is a locally-run, open-source CLI designed for AI agents. Use them on their own or combine them — for example, bitwarden-use fetches a password and hands it to chrome-use to log in, and cookie-use then saves that login state to reuse across profiles.

Members at a glance

A one-line summary and the real repo for each tool. To go deeper on any one, open its GitHub repo.

🌐 chrome-use

Drives your real, already-logged-in Chrome. It shares your existing sessions and anti-bot systems can't detect it — because it is your real browser.

📱 iphone-use

Drives your real iPhone. Operate iOS apps with no API, export data that only lives on the phone, tap/type/scroll/screenshot.

🔐 bitwarden-use

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

🍪 cookie-use

An encrypted, site-agnostic multi-account session vault: save, switch, and inject multiple login states for a website.

ℹ️ More tools

The full *-use family lives in one plugin marketplace, leeguooooo/plugins — all 9 *-use repos in one place.

chrome-use — drive real Chrome

The family's workhorse. It connects any agent (Claude Code, Cursor, Codex, or your own script) to the Chrome you're already using — a browser extension plus a native-messaging channel, no debug port, reusing your existing cookies. Install with one command:

install

# Download the prebuilt binary for your platform from the latest GitHub Release
$ curl -fsSL https://raw.githubusercontent.com/leeguooooo/chrome-use/main/install.sh | sh

Wrap the skill into any agent runner (Claude Code: prefer the plugin marketplace — the whole *-use family lives in leeguooooo/plugins):

skill

# Claude Code
> /plugin marketplace add leeguooooo/plugins
> /plugin install chrome-use@leeguooooo-plugins
# other runners
$ npx skills add leeguooooo/chrome-use -g

After installing the Chrome Web Store extension, register the native-messaging host once, and then you can take over your real browser:

bash

# Register the native-messaging host (only once)
$ chrome-use extension install
$ chrome-use open https://x.com/home

✅ Go deeper on chrome-use

Start from the Overview, or jump straight to Drive Real Chrome (extension) to understand how the extension + native messaging take over. For why it works this way, see the comparison with headless and anti-detection notes.

bitwarden-use + cookie-use — let the agent log in with an identity

Two login-related tools that sit right upstream and downstream of chrome-use. bitwarden-use pulls passwords, 2FA, and passkeys from your Bitwarden vault and hands them to the agent to complete a real credential login; cookie-use treats the login state itself as an asset: encrypting it into a local vault so you can switch and inject it across Chrome profiles anytime.

In the chrome-use test suite, you can inject a login state saved by cookie-use directly with account:, so every case starts from an "already logged in" state:

smoke.yaml

# smoke.yaml
suite: chatgpt smoke
setup:
  - account: chatgpt/huayue          # inject a cookie-use login state (optional)
cases:
  - name: home loads logged in
    steps:
      - open: https://chatgpt.com/
      - wait: { load: networkidle }
    assert:
      - url: { contains: chatgpt.com }
      - visible: "#prompt-textarea"

ℹ️ Related docs

For login and credential-injection details on the chrome-use side, see Login & Credentials, and for keeping login state across processes, see Sessions & Persistence.

iphone-use — drive a real iPhone

Some data only lives on the phone: Apple Health, banking apps, IMs with no open API. iphone-use brings the same "take over the real device" idea to iOS — tapping, typing, scrolling, and screenshotting through macOS iPhone Mirroring to operate apps that will never give you an API. Repo: github.com/leeguooooo/iphone-use.

⚠️ Each tool installs separately

Family members share a philosophy, but they're not one monorepo. iphone-use, bitwarden-use, and cookie-use each have their own repo and install steps — follow each one's README. This page is only navigation; it doesn't replace their docs.