Skip to content

BrowserZap 0.5 is out on npm for Windows · Chrome Web Store listing in review · Get started

BrowserZap

Docs

Changelog

Next release

Built and tested; ships once it has been checked in real Chrome.

  • Comment mode: click elements, write what should change, send every note to your agent with components, source files and screenshots.
  • page_console and page_network: your agent reads console errors and failed requests while it debugs your app.
  • file_upload: attach a file to a "Choose file" input, approved per file; key and credential files are refused.
  • Downloads: a click that starts a download says so; browser_downloads lists and waits for files.
  • Microsoft Edge and WSL: setup registers the helper for Edge; agents inside WSL start BrowserZap through Windows.
  • Doctor explains a moved Node, a blocking Chrome policy and a bridge with another secret; new browserzap restart-bridge.
  • The release zip is ready for the Chrome Web Store.

0.5.0 · 29 October 2026

  • Chrome's "started debugging this browser" bar goes away when the agent ends, when you take the tab, and after a minute without agent actions.
  • No more piles of tabs: one main tab per conversation, helper tabs closed when done (browser_close_tab), at most 5 while working and 3 when idle, none after the agent ends. A tab you are looking at, or drag out of the group, is never closed.

0.4.0 · 28 October 2026

The first public release on npm.

  • Your agent works in your own Chrome tab with your logins; every click and fill targets exactly one element.
  • Approvals for submits, payments, deletions and posts; passwords, codes and card numbers handed to you; Stop at any time.
  • One-command setup with no token to copy; Chrome opens itself on the first browser request.
  • Saved workflows: record once, replay with new values, every step re-checked; slow sites, site error pages and step retries handled.
  • browserzap run runs a workflow from the terminal with no agent.