Reuse browser sign-ins

For people who want an approved agent to use websites they're already signed in to.

The agent never uses your everyday browser. It gets a separate Chromium browser that the helper runs, visible by default. You can copy cookies, history and bookmarks into it once. After that the two are independent: signing in or out in one doesn't affect the other, and some sites will ask you to sign in again. Passwords, open tabs, extensions, local storage and Firefox containers are never copied.

Copy your sign-insCopy Anchor Link

You need Node 22.13 or newer, and Chrome, Chromium, Helium, Edge or Brave installed to run the agent's browser.

1. Run ezremote browser list to see your browsers and profile IDs.
2. Quit the browser you're copying from, then run ezremote browser import firefox 1 with your browser and profile ID. A single profile needs no ID.
3. Approve the prompt. Any agent with Browser permission on this computer can then use the copied accounts.
4. Note the profile UUID it prints. ezremote browser profiles lists your copies.

The copy stays in the helper's private ~/.ezremote/browser-profiles/ folder and never reaches the ezremote service. The import reports cookie counts, never values. A copy grants no Browser permission by itself.

To delete a copy, close the agent's browser and run ezremote browser remove PROFILE_UUID. Signing out in your own browser doesn't sign the copy out, so remove the copy or end the session from the site's settings.

Which browsers workCopy Anchor Link

You can copy from Chrome, Chromium, Edge, Brave, Vivaldi, Opera, Arc, Dia, Helium, Firefox, Zen, LibreWolf or Safari, including Firefox Snap and Flatpak on Linux. Only profiles with cookies appear.

• macOS: Chromium-family browsers may ask to unlock their Keychain item. Choose Allow, not Always Allow. Safari needs Full Disk Access for the terminal running the helper; grant it, retry, then remove it if you like.
• Linux: newer Chromium cookies need secret-tool and an unlocked keyring, or they are skipped.
• Windows: profiles with app-bound encryption, which ordinary Chrome and Edge may use, are refused. Sign in by hand in the agent's browser instead.

Partitioned, container and private cookies are skipped. Bookmarks land flat on the bookmarks bar. Import sizes are in limits. A clean copy still doesn't guarantee every site keeps you signed in.

The agent's browserCopy Anchor Link

Set EZREMOTE_BROWSER_HEADLESS=1 on the computer to hide the window. Set EZREMOTE_BROWSER_EXECUTABLE to a full Chromium build's path to choose one; chrome-headless-shell is refused because it drops session cookies. Otherwise the helper uses an installed browser, or downloads Chrome for Testing on first use, which needs unzip or bsdtar on Linux.

The helper hides Chromium's automation banner and sets navigator.webdriver to false, with no other disguise. Some sites may still detect automation.

For agentsCopy Anchor Link

Call browser_call with name: "profiles/list" and deviceId, then pass the chosen UUID as profile on every call:

{
  "deviceId": "COMPUTER_UUID",
  "profile": "IMPORTED_PROFILE_UUID",
  "name": "tools/list"
}

Without profile, calls use the helper's default browser. Only the person can import, on the computer, so give them the commands above. Use the computer has the other browser rules.