Browser

Use Bash to run the Browser internal CLI when a task requires a real page in Puffer's managed CEF/Chromium browser tab: opening a page, switching tabs, inspecting visible UI, clicking controls, filling fields, pressing keys, uploading files, capturing screenshots, evaluating page JavaScript, or checking page text. Browser is not a model tool and must not be requested as a provider tool call. Run Browser commands as browser ... inside Bash.

Target: $target

Workflow:

1. Resolve login credentials when the task involves signing in.

   • Before asking the user for credentials or attempting manual login, call RequestSecret with action: "search" using the site name, domain, origin, visible username/email hint, or login URL.
   • If exactly one relevant credential is available, request it by id/name and use the returned non-secret username metadata for email, phone, username, or account fields. Use the returned PUFFER_SECRET_... placeholder only in the browser command that fills the password, token, or other secret-value field. Never print the secret value.
   • If multiple matches are available, choose only when the metadata is unambiguous; otherwise ask the user which stored credential to use.
   • If no matching credential exists and login cannot proceed without one, call RequestSecret with action: "collect", a clear name, origin, optional username, and a short prompt so the user can enter the value into a masked secret prompt. Use the returned PUFFER_SECRET_... placeholder; do not ask the user to paste passwords, tokens, cookies, or API keys into chat or AskUserQuestion.

2. Open or find the tab.

   • browser list lists tabs for the current agent session.
   • browser open https://example.com --label docs --width 1280 --height 900 opens or reuses a managed browser tab.
   • browser tab new https://example.com --label scratch forces a fresh tab.
   • browser tab focus t1 switches the active agent-facing tab handle.
   • Treat DOM readiness as the page-ready signal; a single snapshot is enough to start working. Do not wait for full network idle unless the user explicitly asks to debug network quiescence or a page-specific workflow requires all background requests to stop.

3. Snapshot once to get your bearings.

   • browser snapshot --tab-id t1 returns the visible text and fresh refs like @e1.
   • One snapshot lists every interactive ref currently in the viewport — enough to plan a whole form or section. You do not need to snapshot before each field.
   • Refs stay valid until the page changes. Re-snapshot only after a navigation or when an action reports the page changed — not after every action (see step 5).

4. Act on refs in batches, and trust the result.

   • Fill or click every field in a form section back-to-back from the same snapshot, then move on — do not snapshot between fields.
   • Each action returns its result: many actions report the resulting page state (current url, title, and refs); read that returned state to decide your next move instead of taking a separate snapshot. When an action returns only a brief success confirmation, trust it — a silent success means it worked.
   • browser click @e3 --tab-id t1 clicks an element from the latest snapshot.
   • browser focus @e3 --tab-id t1 focuses an element without clicking it.
   • browser fill @e5 "hello" --tab-id t1 replaces text in an editable control. Use this for known final values in email, username, password, search, and address fields.
   • browser type "hello" --ref @e5 --tab-id t1 focuses a ref and inserts/appends text. Do not use this to replace a field value.
   • browser scroll-into-view @e5 --tab-id t1 centers a ref before interacting when needed.
   • browser select @e6 "New York" --tab-id t1 chooses one native <select> option by exact value or label.
   • browser upload @e9 ./file.pdf --tab-id t1 attaches one or more files to a file input.
   • browser check @e7 --tab-id t1 and browser uncheck @e7 --tab-id t1 toggle checkbox-like controls.
   • browser press Enter --tab-id t1 sends a key.

5. Snapshot again only when the page actually changed.

   • Take a fresh snapshot after a navigation, a form submit that loads a new step, or a reload — so you get fresh refs for the new content. An action result that reports a new url/page is your cue.
   • Do NOT re-snapshot to "verify" an in-place fill, click, check, or selection that already returned success.
   • If a later action fails because a ref is missing or has moved — the page changed on its own after an earlier action (async validation, a revealed or removed field) — take one fresh snapshot and continue from the new refs. Never reuse a ref id from an earlier snapshot once the page has changed.
   • Do NOT scroll up and down repeatedly to hunt for an element. The snapshot lists the refs in the current viewport; if a control like a "Pay" or "Continue" button is not among them, scroll once toward where it belongs (usually the bottom of the form) and snapshot once — never loop scroll+snapshot. Use browser scroll-into-view @e5 to center a ref you already have.
   • Prefer refs over brittle coordinates, and prefer the current tab id or label over positional assumptions.

Global options:

• browser --json ... prints machine-readable JSON.
• browser --session-id <id> ... uses another root browser session.
• Most page and ref commands accept --tab-id t1, --width 1280, and --height 900.

Tab and session commands:

• browser list
• browser open [url] [--tab-id t1] [--label docs] [--width 1280] [--height 900]
• browser tab list
• browser tab new [url] [--tab-id t2] [--label scratch] [--width 1280] [--height 900]
• browser tab focus t1 or browser tab select t1
• browser tab close [t1]
• browser close --tab-id t1
• browser close --group
• browser quit or browser exit

Navigation commands:

• browser navigate https://example.com --tab-id t1
• browser goto https://example.com --tab-id t1
• browser reload --tab-id t1
• browser back --tab-id t1
• browser forward --tab-id t1

Inspection commands:

• browser snapshot --tab-id t1
• browser screenshot --tab-id t1
• browser screenshot ./page.png --annotate --tab-id t1
• browser screenshot --screenshot-dir .puffer/screenshots --screenshot-format jpeg --screenshot-quality 90 --tab-id t1
• browser eval "document.title" --tab-id t1 or browser evaluate "document.title" --tab-id t1

Interaction commands:

• browser click @e3 --tab-id t1
• browser dblclick @e3 --tab-id t1
• browser hover @e3 --tab-id t1
• browser focus @e3 --tab-id t1 or browser focus-ref @e3 --tab-id t1
• browser fill @e5 "hello" --tab-id t1
• browser select @e6 "New York" --tab-id t1
• browser upload @e9 ./one.png ./two.png --tab-id t1
• browser check @e7 --tab-id t1
• browser uncheck @e7 --tab-id t1
• browser type "hello" --tab-id t1 appends text at the current cursor
• browser type "hello" --ref @e5 --tab-id t1 focuses the ref and appends text
• browser press Enter --tab-id t1 or browser key Enter --tab-id t1
• browser keydown Shift --tab-id t1
• browser keyup Shift --tab-id t1
• browser keyboard type "hello" --tab-id t1
• browser keyboard insert-text "hello" --tab-id t1
• browser scroll down 800 --tab-id t1
• browser scroll up 600 --tab-id t1
• browser scroll left 400 --tab-id t1
• browser scroll right 400 --tab-id t1
• browser scroll-into-view @e5 --tab-id t1 or browser scrollinto @e5 --tab-id t1

The Browser CLI controls the same daemon-managed CEF/Chromium sessions used by the Browser tab. v1 tabs are stable Puffer handles over managed browser sessions; do not assume cookies or storage are shared between tabs unless verified. Use only commands documented here; if a command is missing, inspect the CLI help instead of inventing a command shape.