Set up Vyre

Vyre / Computer / Vyre for Chrome

Vyre for Chrome.

Your own Chrome, driven by your agents.

Vyre for Chrome works in the Chrome you already have open, signed in as you. It reads a page in one call, fills forms, runs a whole workflow build as a single batch and reads DevTools. A send, a post or a payment is held until you approve it, and Esc stops everything.

Install for Claude CodeInstall inside VyreVault fill extension

What it does today.

One extension, a set of tools.

The tools are the same in both versions. In Claude Code they are named chrome_snapshot, chrome_act and so on. In Vyre the names carry dots, such as chrome.snapshot.

Read and act

chrome_snapshot reads the page, its dialogs and every frame in one call. chrome_act and chrome_fill click, type and fill, finding each control by role, name and identifier on a fresh look. chrome_tabs reuses the tab you have open instead of opening one per step.

Do a whole job in one trip

chrome_batch runs a list of steps inside the browser with no round trip between them, and stops at the first failure and says which step. chrome_recipe replays a flow that already worked as one call. chrome_ghl builds GoHighLevel workflows end to end, with waits, retries and verified saves.

Use the site’s own API

chrome_api learns the page’s own calls and runs them from inside the page with your login. A read tries this first. chrome_op teaches a site an operation once, such as readProfile(slug), and calls it by name after that.

Look inside the page

chrome_inspect, chrome_sources, chrome_console and chrome_net read the DOM, scripts, console and network. chrome_eval runs a script that may read with your login and cannot write with it. chrome_screenshot and chrome_point are the last rung.

Stay in control

chrome_plan shows the plan first. chrome_approve asks once for a job with many changes. chrome_send is where you approve a held send. chrome_stop and chrome_resume mirror Esc. chrome_login hands a sign-in page to you.

Safe by default

Passwords, cookies, tokens and session ids are masked before the model sees them. Banks, password managers and sign-in pages are never read or touched. A page with a visible password field never runs a script. Every session writes a masked trace on your computer only.

Way one.

Standalone, for Claude Code.

An MCP server plus a Chrome extension. No Vyre server is needed. It is the same code that runs inside Vyre. The package and the command are called vyre-chrome.

You need

A Mac or a Windows PC, Chrome 116 or newer, Node 22 or newer (nvm and Homebrew installs are fine), and Claude Code. CI also runs it on Linux.

  1. Build the package from the repository. One command makes the release folder.
    git clone --depth 1 https://github.com/vyre-ai/vyre
    node vyre/local/hands-chrome-mac/standalone/build-release.mjs --out ~/vyre-chrome-release
  2. Register the connector with Chrome. The launcher finds Node itself, so it works even when your shell has no node. On Windows run vyre-chrome.cmd install.
    cd ~/vyre-chrome-release/vyre-chrome && ./vyre-chrome install
    Install copies the package to a read-only folder at ~/.vyre-chrome/app, puts the vyre-chrome command in ~/.local/bin, and prints two things you need next: the extension folder and the exact claude mcp add line for your machine.
  3. Load the extension. Open chrome://extensions, turn on Developer mode, press Load unpacked and choose the folder install printed (~/.vyre-chrome/app/extension). Its id must read jichfmdmnhaphgemkiehddkfcecpncib. The connector only talks to that id. Install waits up to a minute and says “Connected” when the extension answers. If Chrome was already open, it may need one quit and reopen.
  4. Add it to Claude Code, once. Copy the line install printed. It has this shape:
    claude mcp add vyre-chrome -- "<node>" "$HOME/.vyre-chrome/app/standalone/cli.mjs" mcp
  5. Check it. Start Claude Code and ask it to run chrome_status. It should say connected. vyre-chrome doctor checks the whole path from a terminal and names the one fix.

Who approves what

There is no Gate in the standalone version. Claude Code’s own permissions are the approval. Allow the read and act tools if you want it to work without asking. Never put chrome_send or chrome_resume in an allow list: they are where you approve. If your Claude Code can show a question from a tool, the server asks you itself, showing the site, the button and the field values, and a no sends nothing.

Settings and removal

vyre-chrome config learn on|off sets site learning (on by default). vyre-chrome config confirm-sends on|off sets the questions. vyre-chrome logs off stops the trace. vyre-chrome uninstall removes the connector, --purge also deletes the logs. Then remove the extension in chrome://extensions. Browsers: Chrome, Chromium, Brave, Edge, and on a Mac Dia and Arc.

The full README, including the GoHighLevel playbook, is in local/hands-chrome-mac/standalone. Chrome shows two bars you cannot hide: a warning about developer-mode extensions at start, and “started debugging this browser” while a tab is being driven.

Way two.

Native, inside Vyre.

The Vyre Computer extension, with the Gate, Needs you and your agents’ grants around it. This is the way to give a named agent your Chrome.

  1. Run Vyre on your Mac. The Mac app with a home, or a Mac server. The two Chrome versions do not run side by side: the standalone server refuses to start while Vyre is running, so use one or the other.
  2. Register the connector. Run the Chrome setup once:
    vyre call chrome.install '{}'
    It registers the connector with each supported browser it finds and prints the steps you do in the browser.
  3. Load the extension. In chrome://extensions turn on Developer mode, press Load unpacked and choose the folder Vyre printed (the extension is local/hands-chrome-mac/extension in the repository). Click its toolbar icon: it says whether it is connected and, if not, why.
  4. Let an agent use it. You hold the grant yourself. A named agent holds one you give it. Before its first action it must post its plan, and a refusal says so: plan_first.

What native adds

A held send becomes a card in Needs you, of kind act, with the site, the control and the field values. A panel shows the plan and its steps as they run, and you can interject by typing or voice, retext a step that has not started, or pause. Chrome raises a notification when it needs you. Site learning shows in Memory under Sites, where you can see and forget any of it.

The same on both

The tools, the extension code, the URL floor, the redaction, the script guard, the stop and the trace. Only the approval differs: the Gate in Vyre, chrome_send and Claude Code’s permissions in the standalone version.

The sign-in half.

The Vault fill extension, so no one types a password.

Vyre for Chrome never types a password. You do, or this extension does, from your own Vault. It fills logins, cards and addresses and answers passkey requests in Chrome, Arc, Edge and Brave, and fills logins in Firefox. It talks to one address only, your Vyre fill listener, and never sends page content.

  1. Turn on the fill listener. Set vault.fill in config.json, for example { "host": "127.0.0.1", "port": 7788 }, then restart Vyre. On a server, put it behind your own address.
  2. Load the extension. In chrome://extensions (or arc://, edge://, brave://extensions) turn on Developer mode, press Load unpacked and choose modules/vault-extension. For Firefox 121 or later, run node modules/vault-extension/build.mjs and load dist/firefox from about:debugging.
  3. Pair it. Run vyre vault pair. It prints an 8-character code that works once, for 5 minutes. Enter the address and the code in the extension’s popup. vyre vault devices lists paired browsers and revoking one ends it at once.
  4. Use it. Open the popup on a login page, unlock with Touch ID through the Mac app (or a passphrase on a machine without it), and press Fill. One proof opens a fill window of 30 minutes that does not extend with use. Cmd+Shift+L fills the page’s login from the keyboard. Only logins whose hosts include the page’s exact origin are offered.

It can also offer to save an API key a page shows you once, after you tap Save, and to save a login you just used. Detail is in modules/vault-extension.

Coming in 0.5.2

Three pieces become one.

Today the password extension, the Chrome control extension and the standalone server are separate. The 0.5.2 plan merges them into one extension for Chrome first, then Edge, Brave and Arc. It signs in like a device of yours, shows up in Devices and stops working when you remove it there. Chats can then ask to use that Chrome, with Esc and the toolbar as the stop, and a Vyre chat can open in Chrome’s side panel. See the 0.5.2 plan, items 15 to 19.

Connects to

Read how it works.

The architecture of Chrome controlBack to Vyre Computer