Skip to content
fastbrowsefastbrowse

Browsers and logins

Browser agent logins without sharing passwords

Three ways to let a fastbrowse run act in your account: your own signed-in Chrome, a cloud profile, or a login typed from a Bitwarden vault.

·verified against v0.11.0 on ·this post’s source·all posts

How a scoped secret is typedThe model asks to type the secret named password. Code checks that the page is on the declared origin; if so it types the value and redacts it from the result, otherwise the value is not typed.NOYESModeltype passwordOrigin checksaucedemo.com?Typedfrom $SAUCE_PASSWORDNot typedany other originRedactedresult, events, tracesTHE MODEL NEVER SEESthe value, only its name--secret password=SAUCE_PASSWORD@https://www.saucedemo.com
The model names the secret. Code types its value only on the origin it was declared for, and redacts it from everything the run returns.

fastbrowse offers three ways to let a run act in your account. In order of how much you hand over:

  1. Your own Chrome, already signed in.
  2. A cloud profile someone signed into once.
  3. A secret typed from a vault when a field needs it.

Use the Chrome you are signed in to

The command line runs a browser task in your own Chrome through the fastbrowse extension, so every site you are signed in to is already open to the run. Set it up once: run fastbrowse extension install, then add the extension from the Chrome Web Store.

fastbrowse "Add a UGREEN USB-A to USB-C cable, 2m, to my cart." --start https://www.amazon.com/

The agent never receives a password, because the session is already in your Chrome. With no extension connected, the run ends unavailable before it spends anything.

To keep a signed-in profile apart from your everyday Chrome, use an SDK. The command line refuses --profile and --headed, and the Python SDK takes them in LocalChrome. Sign in on the first run, then reuse the directory:

from pathlib import Path

from fastbrowse import run_task
from fastbrowse.models import LocalChrome

await run_task(
    "Add a UGREEN USB-A to USB-C cable, 2m, to my cart.",
    start="https://www.amazon.com/",
    chrome=LocalChrome(profile=Path.home() / ".fastbrowse" / "amazon", headed=True),
)

headed=True is needed for the first run only. A Chrome that is already running works too, over its DevTools port from an SDK: see connect an agent to a running Chrome over CDP.

Use a cloud profile

With --cloud, --cloud-profile runs as a profile someone signed into once. The run inherits its cookies, and no model sees a credential. A cloud browser is billed for its time, separately from any cap on model spend.

Type the login from a vault

With the Bitwarden CLI unlocked, --bitwarden ITEM types the vault login for that item.

export BW_SESSION="$(bw unlock --raw)"
fastbrowse "Add a UGREEN USB-A to USB-C cable, 2m, to my cart." \
  --start https://www.amazon.com/ --bitwarden Amazon

How secrets are handled

Whether a value comes from a vault or the environment:

A password field is typed only from a stored secret. To change a password, add the new one as an origin-scoped secret named new_password, refer to it in the task, and pass --authorize.

Signed-in sites and secrets is the reference for profiles, vault items and secrets. Command-line flags lists --secret and --authorize, and the safety model explains the authorization gate and its limits.

Next: your first run.

hosted

Run fastbrowse over an API

The same agent behind an API. Keys, secrets, run history and spend limits live in the console. Free to start.

create an account·plans and pricing