Docs

Configuration

BrowserZap works without configuration. Environment variables go in your agent's MCP entry for BrowserZap ("env": { … }), so different agents can have different limits.

Environment variables

`BROWSERZAP_ALLOWED_ORIGINS`	Comma-separated sites the agent may act on, e.g. https://app.example.com. Everything else is refused (POLICY_BLOCKED).
`BROWSERZAP_PROFILE`	Pin this agent to one Chrome profile, by the name you gave it in the side panel (e.g. Work).
`BROWSERZAP_AUTO_LAUNCH`	0 stops BrowserZap opening Chrome when it is closed.
`BROWSERZAP_UPLOAD_DIR`next release	Limit file_upload to files inside this folder.
`BROWSERZAP_DOWNLOAD_DIR`next release	Where Chrome saves downloads, if you changed it (default: your Downloads folder).
`BROWSERZAP_SCREENSHOT_DAYS`	Days to keep screenshots (default 7; 0 deletes them when the MCP server exits).
`BROWSERZAP_FEEDBACK_DAYS`next release	Days to keep Comment mode batches (default 7).
`BROWSERZAP_LOG`	Session log: standard (default), verbose (adds summaries) or off. Never contains what you type.
`BROWSERZAP_BRIDGE_PORT`	Port for the local bridge (default 9334); set the same port in the side panel settings.
`BROWSERZAP_HOME`	Use another folder for BrowserZap’s data (testing, separate setups).

"browserzap": {
  "command": "node",
  "args": ["C:\\…\\bridge-server\\index.js"],
  "env": { "BROWSERZAP_ALLOWED_ORIGINS": "https://app.example.com" }
}

Commands

`browserzap setup`	One-time setup: register the helper, copy the extension, offer MCP entries for your clients. Safe to repeat.
`browserzap doctor`	Check the helper registration, the extension id, the launcher and the bridge; each failure says what to do.
`browserzap restart-bridge`next release	Replace a bridge that will not pair (another install’s secret, an old version).
`browserzap run <workflow> --params rows.csv`	Run a saved workflow with no agent, one run per row (more than one row is Pro).
`browserzap uninstall`	Remove the helper registration and the extension copy; keeps your data.
`browserzap uninstall --purge`	Also remove BrowserZap’s data folder (cannot be undone).
`browserzap --help`	All commands, and the exact MCP configuration for your paths.

Where your data lives

%LOCALAPPDATA%\BrowserZap on Windows: the pairing secret, workflows, run reports, screenshots, Comment mode batches, the session log and your licence. Readable only by your user account. See privacy for what each one holds and never holds.