Docs

Edge, WSL, macOS and Linux

Where	Status
Windows 10 / 11 + Google Chrome	Supported (0.5)
Microsoft Edge on Windows	Next release next release
Agent inside WSL, Chrome on Windows	Next release next release
macOS	Planned; the code exists and is tested in CI, not yet on a real Mac
Linux	Planned; tested in CI
ChromeOS	Not possible: it has no native messaging

The extension is the same on every system. What differs is only how the small local helper registers with the browser.

Microsoft Edge next release

Edge installs extensions from the Chrome Web Store and loads the same unpacked folder, with the same extension id. From the next release, browserzap setup registers the helper for Edge as well as Chrome, and browserzap doctor checks both. Auto-launch still opens Chrome.

From WSL next release

Many people run Claude Code inside WSL while Chrome runs on Windows. BrowserZap stays on Windows (its bridge listens on Windows' own loopback address and is never opened to the WSL network); your agent in WSL starts it through Windows interop:

On Windows: npm install -g browserzap, then browserzap setup.
In WSL:

claude mcp add browserzap -- cmd.exe /c browserzap

Other clients: command cmd.exe, arguments ["/c", "browserzap"]. Setup prints this line when your machine has WSL, and starting BrowserZap inside WSL explains what to do instead.

macOS and Linux

Setup, the helper and auto-launch already have code for both, and the test suite runs on macOS and Linux on every change. They become supported once they have been tested on real machines; until then the npm package installs on Windows only.