BrowserForge MCP v0.2.0

What's new in 0.2.0

• Dashboard. browserforge dashboard opens a read-only local page: connected browsers, MCP sessions and every tool, plugins with the permissions you approved, skills, recorded flows and how the local models are doing. It has its own token (the MCP token cannot open it), only the page itself may call its data, and a strict Content-Security-Policy applies. See docs/DASHBOARD.md.
• Windows installer. BrowserForge-Setup-0.2.0.exe brings its own Node.js 22 (checksum-pinned), needs no administrator rights, adds the browserforge command to your PATH and keeps your settings when you uninstall. It is built and smoke-tested on a real Windows runner (install, run, dashboard, uninstall). It is not code-signed yet, so Windows SmartScreen shows "Windows protected your PC": choose More info, then Run anyway.
• Flows. flow_task_begin / flow_task_end record a scripted task as one clean flow with its outcome, flow_prune tidies old flows, and recorded values are scrubbed.
• Shadow DOM. The extension reads and drives open shadow roots (web-component forms such as SmartRecruiters). Closed shadow roots are still invisible.
• Docs. New docs/VISION.md, a wiki and a public roadmap board. The setup report now points to the store pages.

Install

• Windows: run BrowserForge-Setup-0.2.0.exe (attached to this release a few minutes after it is published).
• Linux / macOS: npm install -g ./browserforge-mcp-0.2.0.tgz, then browserforge setup. (The package is not on the npm registry yet: issue #3.)
• Extension: Chrome Web Store · Firefox Add-ons. The store versions are updated separately and may still be 0.1.0; the extension zips below are the 0.2.0 builds.

Files

browserforge-mcp-0.2.0.tgz (the program), browserforge-{chrome,chrome-bodies,firefox}-0.2.0.zip (unpacked-extension builds), *-store-0.2.0.zip (the files submitted to the Chrome Web Store), browserforge-source-0.2.0.zip (source for Firefox review).

Everything has been run by hand only on Linux; Windows and macOS are covered by CI. Please report problems.

BrowserForge MCP v0.1.0

First public release of BrowserForge MCP: a Firefox and Chrome extension plus a local MCP server. It lets your AI agent (Claude Code, Codex, or any MCP client) use your real browser, and you approve every submit, send, upload and password.

Install

npm install -g browserforge-mcp
browserforge setup

browserforge setup prints where to load the extension and how to connect your agent. See docs/INSTALL.md.

Files

File	What it is
browserforge-mcp-0.1.0.tgz	The program, as one bundled file. Install it with npm install -g ./browserforge-mcp-0.1.0.tgz
browserforge-firefox-0.1.0.zip	The Firefox add-on (unsigned until addons.mozilla.org approves it)
browserforge-chrome-0.1.0.zip	The Chrome / Edge / Brave extension, to unzip and Load unpacked
browserforge-chrome-bodies-0.1.0.zip	The Chrome build that also captures response bodies (needs the debugger permission)
*-store-0.1.0.zip	The same two Chrome builds as uploaded to the Chrome Web Store (no manifest key)
browserforge-source-0.1.0.zip	Source of this tag

Status

This is a pre-release.

• Linux is the only system it has been run on.
• Windows and macOS have known test failures in CI.
• The store listings are under review.

Read docs/LIMITATIONS.md, docs/SECURITY.md and docs/PRIVACY.md.