Repository navigation
Releases: anvai-labs/agentbrowser
Release list
v1.27.1
AgentBrowser v1.27.1
AgentBrowser ships a first-class CLI, a service and an optional MCP
adapter. Point the CLI at a reachable service with --base-url, or set
AGENTBROWSER_BASE_URL for MCP (default http://localhost:5709). The MCP
executable is only the stdio adapter, not the service.
See the versioned changelog
for included capabilities and qualification limits.
The service is now installable too: agentbrowser-server-<target>.tar.gz
is a self-contained server build (pruned production node_modules +
compiled dist/) whose every artifact passed extracted-package acceptance:
real Chromium navigation/snapshot/action, valid screenshot/PDF bytes,
HTTP/TLS downloads, denial/cancellation controls and matching CLI/MCP calls.
Stock-launcher default denial and instrumented snapshot recovery are
distinct checks. This is not hostile-browser containment evidence.
tar -xzf agentbrowser-server-<target>.tar.gz && ./server/agentbrowser-server
# needs Node 22 or newer plus a compatible Chromium already installed under
# PLAYWRIGHT_BROWSERS_PATH; the archive launcher does not download it.
# Linux hosts must also provide Chromium's platform libraries.Homebrew users get the server, CLI and MCP in one command:
brew install anvai-labs/tap/agentbrowser
(brew services start anvai-labs/tap/agentbrowser runs the service).
Windows users get all three in agentbrowser-windows-x64.zip
(winget install AnvaiLabs.AgentBrowser, or extract the zip anywhere):
agentbrowser-server.exe runs the service on the bundled Node.js
runtime (node\) and downloads its Chromium on first start
(--install-browser pre-provisions it).
agentbrowser-server --version
agentbrowser-server # first start downloads Chromium (~300 MB)Smoke coverage
| Artifact | Stdio smoke |
|---|---|
| agentbrowser-mcp-darwin-arm64 | run natively on the build runner |
| agentbrowser-mcp-darwin-x64 | run via Rosetta on the arm64 runner |
| agentbrowser-mcp-linux-x64 | run natively on the build runner |
| agentbrowser-mcp-linux-arm64 | run natively on the ARM build runner |
| agentbrowser-mcp-windows-x64.exe | run natively on the build runner |
The CLI (agentbrowser-cli-<target>) ships from this release too —
--version and --help smoke-tested wherever the runner can execute it (same
targets/omissions as the MCP binary).
Each smoke ran initialize + tools/list against the compiled
artifact and required the complete unbound catalog and the exact release version
in serverInfo.
Server acceptance uses Node 24.21.0 on native Linux x64/ARM and Darwin ARM.
The Darwin x64 tarball is exercised on ARM Node with Rosetta x64 clients;
this is not native Intel server-runtime proof. The Windows bundle was
assembled and smoke-tested on a hosted Windows runner from a clean room
outside the build checkout: first start, a real Chromium session through
the CLI and MCP executables, launcher-kill cleanup, invocation through
a symlink (winget's Links directory), and a first start that downloads
Chromium itself.
Install
# verify against sha256sums.txt after download
chmod +x agentbrowser-mcp-<target># ~/.victor/mcp.yaml - no Node, no repo checkout
mcpServers:
agentbrowser:
command: /usr/local/bin/agentbrowser-mcp
env:
AGENTBROWSER_BASE_URL: http://localhost:5709Built with bun 1.4.0.
v1.27.0
AgentBrowser v1.27.0
AgentBrowser ships a first-class CLI, a service and an optional MCP
adapter. Point the CLI at a reachable service with --base-url, or set
AGENTBROWSER_BASE_URL for MCP (default http://localhost:5709). The MCP
executable is only the stdio adapter, not the service.
See the versioned changelog
for included capabilities and qualification limits.
The service is now installable too: agentbrowser-server-<target>.tar.gz
is a self-contained server build (pruned production node_modules +
compiled dist/) whose every artifact passed extracted-package acceptance:
real Chromium navigation/snapshot/action, valid screenshot/PDF bytes,
HTTP/TLS downloads, denial/cancellation controls and matching CLI/MCP calls.
Stock-launcher default denial and instrumented snapshot recovery are
distinct checks. This is not hostile-browser containment evidence.
tar -xzf agentbrowser-server-<target>.tar.gz && ./server/agentbrowser-server
# needs Node 22 or newer plus a compatible Chromium already installed under
# PLAYWRIGHT_BROWSERS_PATH; the archive launcher does not download it.
# Linux hosts must also provide Chromium's platform libraries.Homebrew users get the server, CLI and MCP in one command:
brew install anvai-labs/tap/agentbrowser
(brew services start anvai-labs/tap/agentbrowser runs the service).
Windows users get all three in agentbrowser-windows-x64.zip
(winget install AnvaiLabs.AgentBrowser, or extract the zip anywhere):
agentbrowser-server.exe runs the service on the bundled Node.js
runtime (node\) and downloads its Chromium on first start
(--install-browser pre-provisions it).
agentbrowser-server --version
agentbrowser-server # first start downloads Chromium (~300 MB)Smoke coverage
| Artifact | Stdio smoke |
|---|---|
| agentbrowser-mcp-darwin-arm64 | run natively on the build runner |
| agentbrowser-mcp-darwin-x64 | run via Rosetta on the arm64 runner |
| agentbrowser-mcp-linux-x64 | run natively on the build runner |
| agentbrowser-mcp-linux-arm64 | run natively on the ARM build runner |
| agentbrowser-mcp-windows-x64.exe | run natively on the build runner |
The CLI (agentbrowser-cli-<target>) ships from this release too —
--version and --help smoke-tested wherever the runner can execute it (same
targets/omissions as the MCP binary).
Each smoke ran initialize + tools/list against the compiled
artifact and required the complete unbound catalog and the exact release version
in serverInfo.
Server acceptance uses Node 24.21.0 on native Linux x64/ARM and Darwin ARM.
The Darwin x64 tarball is exercised on ARM Node with Rosetta x64 clients;
this is not native Intel server-runtime proof. The Windows bundle was
assembled and smoke-tested on a hosted Windows runner from a clean room
outside the build checkout: first start, a real Chromium session through
the CLI and MCP executables, launcher-kill cleanup, invocation through
a symlink (winget's Links directory), and a first start that downloads
Chromium itself.
Install
# verify against sha256sums.txt after download
chmod +x agentbrowser-mcp-<target># ~/.victor/mcp.yaml - no Node, no repo checkout
mcpServers:
agentbrowser:
command: /usr/local/bin/agentbrowser-mcp
env:
AGENTBROWSER_BASE_URL: http://localhost:5709Built with bun 1.4.0.
v1.26.0
AgentBrowser v1.26.0
AgentBrowser ships a first-class CLI, a service and an optional MCP
adapter. Point the CLI at a reachable service with --base-url, or set
AGENTBROWSER_BASE_URL for MCP (default http://localhost:5709). The MCP
executable is only the stdio adapter, not the service.
See the versioned changelog
for included capabilities and qualification limits.
The service is now installable too: agentbrowser-server-<target>.tar.gz
is a self-contained server build (pruned production node_modules +
compiled dist/) whose every artifact passed extracted-package acceptance:
real Chromium navigation/snapshot/action, valid screenshot/PDF bytes,
HTTP/TLS downloads, denial/cancellation controls and matching CLI/MCP calls.
Stock-launcher default denial and instrumented snapshot recovery are
distinct checks. This is not hostile-browser containment evidence.
tar -xzf agentbrowser-server-<target>.tar.gz && ./server/agentbrowser-server
# needs Node 22 or newer plus a compatible Chromium already installed under
# PLAYWRIGHT_BROWSERS_PATH; the archive launcher does not download it.
# Linux hosts must also provide Chromium's platform libraries.Homebrew users get the server, CLI and MCP in one command:
brew install anvai-labs/tap/agentbrowser
(brew services start anvai-labs/tap/agentbrowser runs the service).
Windows users get all three in agentbrowser-windows-x64.zip
(winget install AnvaiLabs.AgentBrowser, or extract the zip anywhere):
agentbrowser-server.exe runs the service on the bundled Node.js
runtime (node\) and downloads its Chromium on first start
(--install-browser pre-provisions it).
agentbrowser-server --version
agentbrowser-server # first start downloads Chromium (~300 MB)Smoke coverage
| Artifact | Stdio smoke |
|---|---|
| agentbrowser-mcp-darwin-arm64 | run natively on the build runner |
| agentbrowser-mcp-darwin-x64 | run via Rosetta on the arm64 runner |
| agentbrowser-mcp-linux-x64 | run natively on the build runner |
| agentbrowser-mcp-linux-arm64 | run natively on the ARM build runner |
| agentbrowser-mcp-windows-x64.exe | run natively on the build runner |
The CLI (agentbrowser-cli-<target>) ships from this release too —
--version and --help smoke-tested wherever the runner can execute it (same
targets/omissions as the MCP binary).
Each smoke ran initialize + tools/list against the compiled
artifact and required the complete unbound catalog and the exact release version
in serverInfo.
Server acceptance uses Node 24.21.0 on native Linux x64/ARM and Darwin ARM.
The Darwin x64 tarball is exercised on ARM Node with Rosetta x64 clients;
this is not native Intel server-runtime proof. The Windows bundle was
assembled and smoke-tested on a hosted Windows runner from a clean room
outside the build checkout: first start, a real Chromium session through
the CLI and MCP executables, launcher-kill cleanup, invocation through
a symlink (winget's Links directory), and a first start that downloads
Chromium itself.
Install
# verify against sha256sums.txt after download
chmod +x agentbrowser-mcp-<target># ~/.victor/mcp.yaml - no Node, no repo checkout
mcpServers:
agentbrowser:
command: /usr/local/bin/agentbrowser-mcp
env:
AGENTBROWSER_BASE_URL: http://localhost:5709Built with bun 1.4.0.
v1.25.0
AgentBrowser v1.25.0
AgentBrowser ships a first-class CLI, a service and an optional MCP
adapter. Point the CLI at a reachable service with --base-url, or set
AGENTBROWSER_BASE_URL for MCP (default http://localhost:5709). The MCP
executable is only the stdio adapter, not the service.
See the versioned changelog
for included capabilities and qualification limits.
The service is now installable too: agentbrowser-server-<target>.tar.gz
is a self-contained server build (pruned production node_modules +
compiled dist/) whose every artifact passed extracted-package acceptance:
real Chromium navigation/snapshot/action, valid screenshot/PDF bytes,
HTTP/TLS downloads, denial/cancellation controls and matching CLI/MCP calls.
Stock-launcher default denial and instrumented snapshot recovery are
distinct checks. This is not hostile-browser containment evidence.
tar -xzf agentbrowser-server-<target>.tar.gz && ./server/agentbrowser-server
# needs Node 22 or newer plus a compatible Chromium already installed under
# PLAYWRIGHT_BROWSERS_PATH; the archive launcher does not download it.
# Linux hosts must also provide Chromium's platform libraries.Homebrew users get the server, CLI and MCP in one command:
brew install anvai-labs/tap/agentbrowser
(brew services start anvai-labs/tap/agentbrowser runs the service).
Windows users get all three in agentbrowser-windows-x64.zip
(winget install AnvaiLabs.AgentBrowser, or extract the zip anywhere):
agentbrowser-server.exe runs the service on the bundled Node.js
runtime (node\) and downloads its Chromium on first start
(--install-browser pre-provisions it).
agentbrowser-server --version
agentbrowser-server # first start downloads Chromium (~300 MB)Smoke coverage
| Artifact | Stdio smoke |
|---|---|
| agentbrowser-mcp-darwin-arm64 | run natively on the build runner |
| agentbrowser-mcp-darwin-x64 | run via Rosetta on the arm64 runner |
| agentbrowser-mcp-linux-x64 | run natively on the build runner |
| agentbrowser-mcp-linux-arm64 | run natively on the ARM build runner |
| agentbrowser-mcp-windows-x64.exe | run natively on the build runner |
The CLI (agentbrowser-cli-<target>) ships from this release too —
--version and --help smoke-tested wherever the runner can execute it (same
targets/omissions as the MCP binary).
Each smoke ran initialize + tools/list against the compiled
artifact and required the complete unbound catalog and the exact release version
in serverInfo.
Server acceptance uses Node 24.21.0 on native Linux x64/ARM and Darwin ARM.
The Darwin x64 tarball is exercised on ARM Node with Rosetta x64 clients;
this is not native Intel server-runtime proof. The Windows bundle was
assembled and smoke-tested on a hosted Windows runner from a clean room
outside the build checkout: first start, a real Chromium session through
the CLI and MCP executables, launcher-kill cleanup, invocation through
a symlink (winget's Links directory), and a first start that downloads
Chromium itself.
Install
# verify against sha256sums.txt after download
chmod +x agentbrowser-mcp-<target># ~/.victor/mcp.yaml - no Node, no repo checkout
mcpServers:
agentbrowser:
command: /usr/local/bin/agentbrowser-mcp
env:
AGENTBROWSER_BASE_URL: http://localhost:5709Built with bun 1.4.0.
v1.24.0
AgentBrowser v1.24.0
AgentBrowser ships a first-class CLI, a service and an optional MCP
adapter. Point the CLI at a reachable service with --base-url, or set
AGENTBROWSER_BASE_URL for MCP (default http://localhost:5709). The MCP
executable is only the stdio adapter, not the service.
See the versioned changelog
for included capabilities and qualification limits.
The service is now installable too: agentbrowser-server-<target>.tar.gz
is a self-contained server build (pruned production node_modules +
compiled dist/) whose every artifact passed extracted-package acceptance:
real Chromium navigation/snapshot/action, valid screenshot/PDF bytes,
HTTP/TLS downloads, denial/cancellation controls and matching CLI/MCP calls.
Stock-launcher default denial and instrumented snapshot recovery are
distinct checks. This is not hostile-browser containment evidence.
tar -xzf agentbrowser-server-<target>.tar.gz && ./server/agentbrowser-server
# needs Node 22 or newer plus a compatible Chromium already installed under
# PLAYWRIGHT_BROWSERS_PATH; the archive launcher does not download it.
# Linux hosts must also provide Chromium's platform libraries.Homebrew users get the server, CLI and MCP in one command:
brew install anvai-labs/tap/agentbrowser
(brew services start anvai-labs/tap/agentbrowser runs the service).
Windows users get all three in agentbrowser-windows-x64.zip
(winget install AnvaiLabs.AgentBrowser, or extract the zip anywhere):
agentbrowser-server.exe runs the service on the bundled Node.js
runtime (node\) and downloads its Chromium on first start
(--install-browser pre-provisions it).
agentbrowser-server --version
agentbrowser-server # first start downloads Chromium (~300 MB)Smoke coverage
| Artifact | Stdio smoke |
|---|---|
| agentbrowser-mcp-darwin-arm64 | run natively on the build runner |
| agentbrowser-mcp-darwin-x64 | run via Rosetta on the arm64 runner |
| agentbrowser-mcp-linux-x64 | run natively on the build runner |
| agentbrowser-mcp-linux-arm64 | run natively on the ARM build runner |
| agentbrowser-mcp-windows-x64.exe | run natively on the build runner |
The CLI (agentbrowser-cli-<target>) ships from this release too —
--version and --help smoke-tested wherever the runner can execute it (same
targets/omissions as the MCP binary).
Each smoke ran initialize + tools/list against the compiled
artifact and required the complete unbound catalog and the exact release version
in serverInfo.
Server acceptance uses Node 24.21.0 on native Linux x64/ARM and Darwin ARM.
The Darwin x64 tarball is exercised on ARM Node with Rosetta x64 clients;
this is not native Intel server-runtime proof. The Windows bundle was
assembled and smoke-tested on a hosted Windows runner from a clean room
outside the build checkout: first start, a real Chromium session through
the CLI and MCP executables, launcher-kill cleanup, invocation through
a symlink (winget's Links directory), and a first start that downloads
Chromium itself.
Install
# verify against sha256sums.txt after download
chmod +x agentbrowser-mcp-<target># ~/.victor/mcp.yaml - no Node, no repo checkout
mcpServers:
agentbrowser:
command: /usr/local/bin/agentbrowser-mcp
env:
AGENTBROWSER_BASE_URL: http://localhost:5709Built with bun 1.4.0.
v1.23.0
AgentBrowser v1.23.0
AgentBrowser ships a first-class CLI, a service and an optional MCP
adapter. Point the CLI at a reachable service with --base-url, or set
AGENTBROWSER_BASE_URL for MCP (default http://localhost:5709). The MCP
executable is only the stdio adapter, not the service.
See the versioned changelog
for included capabilities and qualification limits.
The service is now installable too: agentbrowser-server-<target>.tar.gz
is a self-contained server build (pruned production node_modules +
compiled dist/) whose every artifact passed extracted-package acceptance:
real Chromium navigation/snapshot/action, valid screenshot/PDF bytes,
HTTP/TLS downloads, denial/cancellation controls and matching CLI/MCP calls.
Stock-launcher default denial and instrumented snapshot recovery are
distinct checks. This is not hostile-browser containment evidence.
tar -xzf agentbrowser-server-<target>.tar.gz && ./server/agentbrowser-server
# needs Node 22 or newer plus a compatible Chromium already installed under
# PLAYWRIGHT_BROWSERS_PATH; the archive launcher does not download it.
# Linux hosts must also provide Chromium's platform libraries.Homebrew users get the server, CLI and MCP in one command:
brew install anvai-labs/tap/agentbrowser
(brew services start anvai-labs/tap/agentbrowser runs the service).
Windows users get all three in agentbrowser-windows-x64.zip
(winget install AnvaiLabs.AgentBrowser, or extract the zip anywhere):
agentbrowser-server.exe runs the service on the bundled Node.js
runtime (node\) and downloads its Chromium on first start
(--install-browser pre-provisions it).
agentbrowser-server --version
agentbrowser-server # first start downloads Chromium (~300 MB)Smoke coverage
| Artifact | Stdio smoke |
|---|---|
| agentbrowser-mcp-darwin-arm64 | run natively on the build runner |
| agentbrowser-mcp-darwin-x64 | run via Rosetta on the arm64 runner |
| agentbrowser-mcp-linux-x64 | run natively on the build runner |
| agentbrowser-mcp-linux-arm64 | run natively on the ARM build runner |
| agentbrowser-mcp-windows-x64.exe | run natively on the build runner |
The CLI (agentbrowser-cli-<target>) ships from this release too —
--version and --help smoke-tested wherever the runner can execute it (same
targets/omissions as the MCP binary).
Each smoke ran initialize + tools/list against the compiled
artifact and required the complete unbound catalog and the exact release version
in serverInfo.
Server acceptance uses Node 24.21.0 on native Linux x64/ARM and Darwin ARM.
The Darwin x64 tarball is exercised on ARM Node with Rosetta x64 clients;
this is not native Intel server-runtime proof. The Windows bundle was
assembled and smoke-tested on a hosted Windows runner from a clean room
outside the build checkout: first start, a real Chromium session through
the CLI and MCP executables, launcher-kill cleanup, invocation through
a symlink (winget's Links directory), and a first start that downloads
Chromium itself.
Install
# verify against sha256sums.txt after download
chmod +x agentbrowser-mcp-<target># ~/.victor/mcp.yaml - no Node, no repo checkout
mcpServers:
agentbrowser:
command: /usr/local/bin/agentbrowser-mcp
env:
AGENTBROWSER_BASE_URL: http://localhost:5709Built with bun 1.4.0.
v1.22.0
AgentBrowser v1.22.0
AgentBrowser ships a first-class CLI, a service and an optional MCP
adapter. Point the CLI at a reachable service with --base-url, or set
AGENTBROWSER_BASE_URL for MCP (default http://localhost:5709). The MCP
executable is only the stdio adapter, not the service.
See the versioned changelog
for included capabilities and qualification limits.
The service is now installable too: agentbrowser-server-<target>.tar.gz
is a self-contained server build (pruned production node_modules +
compiled dist/) whose every artifact passed extracted-package acceptance:
real Chromium navigation/snapshot/action, valid screenshot/PDF bytes,
HTTP/TLS downloads, denial/cancellation controls and matching CLI/MCP calls.
Stock-launcher default denial and instrumented snapshot recovery are
distinct checks. This is not hostile-browser containment evidence.
tar -xzf agentbrowser-server-<target>.tar.gz && ./server/agentbrowser-server
# needs Node 22 or newer plus a compatible Chromium already installed under
# PLAYWRIGHT_BROWSERS_PATH; the archive launcher does not download it.
# Linux hosts must also provide Chromium's platform libraries.Homebrew users get the server, CLI and MCP in one command:
brew install anvai-labs/tap/agentbrowser
(brew services start anvai-labs/tap/agentbrowser runs the service).
Windows users get all three in agentbrowser-windows-x64.zip
(winget install AnvaiLabs.AgentBrowser, or extract the zip anywhere):
agentbrowser-server.exe runs the service on the bundled Node.js
runtime (node\) and downloads its Chromium on first start
(--install-browser pre-provisions it).
agentbrowser-server --version
agentbrowser-server # first start downloads Chromium (~300 MB)Smoke coverage
| Artifact | Stdio smoke |
|---|---|
| agentbrowser-mcp-darwin-arm64 | run natively on the build runner |
| agentbrowser-mcp-darwin-x64 | run via Rosetta on the arm64 runner |
| agentbrowser-mcp-linux-x64 | run natively on the build runner |
| agentbrowser-mcp-linux-arm64 | run natively on the ARM build runner |
| agentbrowser-mcp-windows-x64.exe | run natively on the build runner |
The CLI (agentbrowser-cli-<target>) ships from this release too —
--version and --help smoke-tested wherever the runner can execute it (same
targets/omissions as the MCP binary).
Each smoke ran initialize + tools/list against the compiled
artifact and required the complete unbound catalog and the exact release version
in serverInfo.
Server acceptance uses Node 24.21.0 on native Linux x64/ARM and Darwin ARM.
The Darwin x64 tarball is exercised on ARM Node with Rosetta x64 clients;
this is not native Intel server-runtime proof. The Windows bundle was
assembled and smoke-tested on a hosted Windows runner from a clean room
outside the build checkout: first start, a real Chromium session through
the CLI and MCP executables, launcher-kill cleanup, invocation through
a symlink (winget's Links directory), and a first start that downloads
Chromium itself.
Install
# verify against sha256sums.txt after download
chmod +x agentbrowser-mcp-<target># ~/.victor/mcp.yaml - no Node, no repo checkout
mcpServers:
agentbrowser:
command: /usr/local/bin/agentbrowser-mcp
env:
AGENTBROWSER_BASE_URL: http://localhost:5709Built with bun 1.4.0.
v1.21.0
AgentBrowser v1.21.0
AgentBrowser ships a first-class CLI, a service and an optional MCP
adapter. Point the CLI at a reachable service with --base-url, or set
AGENTBROWSER_BASE_URL for MCP (default http://localhost:5709). The MCP
executable is only the stdio adapter, not the service.
See the versioned changelog
for included capabilities and qualification limits.
The service is now installable too: agentbrowser-server-<target>.tar.gz
is a self-contained server build (pruned production node_modules +
compiled dist/) whose every artifact passed extracted-package acceptance:
real Chromium navigation/snapshot/action, valid screenshot/PDF bytes,
HTTP/TLS downloads, denial/cancellation controls and matching CLI/MCP calls.
Stock-launcher default denial and instrumented snapshot recovery are
distinct checks. This is not hostile-browser containment evidence.
tar -xzf agentbrowser-server-<target>.tar.gz && ./server/agentbrowser-server
# needs Node 22 or newer plus a compatible Chromium already installed under
# PLAYWRIGHT_BROWSERS_PATH; the archive launcher does not download it.
# Linux hosts must also provide Chromium's platform libraries.Homebrew users get the server, CLI and MCP in one command:
brew install anvai-labs/tap/agentbrowser
(brew services start anvai-labs/tap/agentbrowser runs the service).
Windows users get all three in agentbrowser-windows-x64.zip
(winget install AnvaiLabs.AgentBrowser, or extract the zip anywhere):
agentbrowser-server.exe runs the service on the bundled Node.js
runtime (node\) and downloads its Chromium on first start
(--install-browser pre-provisions it).
agentbrowser-server --version
agentbrowser-server # first start downloads Chromium (~300 MB)Smoke coverage
| Artifact | Stdio smoke |
|---|---|
| agentbrowser-mcp-darwin-arm64 | run natively on the build runner |
| agentbrowser-mcp-darwin-x64 | run via Rosetta on the arm64 runner |
| agentbrowser-mcp-linux-x64 | run natively on the build runner |
| agentbrowser-mcp-linux-arm64 | run natively on the ARM build runner |
| agentbrowser-mcp-windows-x64.exe | run natively on the build runner |
The CLI (agentbrowser-cli-<target>) ships from this release too —
--version and --help smoke-tested wherever the runner can execute it (same
targets/omissions as the MCP binary).
Each smoke ran initialize + tools/list against the compiled
artifact and required the complete unbound catalog and the exact release version
in serverInfo.
Server acceptance uses Node 24.21.0 on native Linux x64/ARM and Darwin ARM.
The Darwin x64 tarball is exercised on ARM Node with Rosetta x64 clients;
this is not native Intel server-runtime proof. The Windows bundle was
assembled and smoke-tested on a hosted Windows runner from a clean room
outside the build checkout: first start, a real Chromium session through
the CLI and MCP executables, launcher-kill cleanup, invocation through
a symlink (winget's Links directory), and a first start that downloads
Chromium itself.
Install
# verify against sha256sums.txt after download
chmod +x agentbrowser-mcp-<target># ~/.victor/mcp.yaml - no Node, no repo checkout
mcpServers:
agentbrowser:
command: /usr/local/bin/agentbrowser-mcp
env:
AGENTBROWSER_BASE_URL: http://localhost:5709Built with bun 1.4.0.
v1.20.0
AgentBrowser v1.20.0
AgentBrowser ships a first-class CLI, a service and an optional MCP
adapter. Point the CLI at a reachable service with --base-url, or set
AGENTBROWSER_BASE_URL for MCP (default http://localhost:5709). The MCP
executable is only the stdio adapter, not the service.
See the versioned changelog
for included capabilities and qualification limits.
The service is now installable too: agentbrowser-server-<target>.tar.gz
is a self-contained server build (pruned production node_modules +
compiled dist/) whose every artifact passed extracted-package acceptance:
real Chromium navigation/snapshot/action, valid screenshot/PDF bytes,
HTTP/TLS downloads, denial/cancellation controls and matching CLI/MCP calls.
Stock-launcher default denial and instrumented snapshot recovery are
distinct checks. This is not hostile-browser containment evidence.
tar -xzf agentbrowser-server-<target>.tar.gz && ./server/agentbrowser-server
# needs Node 22 or newer plus a compatible Chromium already installed under
# PLAYWRIGHT_BROWSERS_PATH; the archive launcher does not download it.
# Linux hosts must also provide Chromium's platform libraries.Homebrew users get the server, CLI and MCP in one command:
brew install anvai-labs/tap/agentbrowser
(brew services start anvai-labs/tap/agentbrowser runs the service).
Windows users get all three in agentbrowser-windows-x64.zip
(winget install AnvaiLabs.AgentBrowser, or extract the zip anywhere):
agentbrowser-server.exe runs the service on the bundled Node.js
runtime (node\) and downloads its Chromium on first start
(--install-browser pre-provisions it).
agentbrowser-server --version
agentbrowser-server # first start downloads Chromium (~300 MB)Smoke coverage
| Artifact | Stdio smoke |
|---|---|
| agentbrowser-mcp-darwin-arm64 | run natively on the build runner |
| agentbrowser-mcp-darwin-x64 | run via Rosetta on the arm64 runner |
| agentbrowser-mcp-linux-x64 | run natively on the build runner |
| agentbrowser-mcp-linux-arm64 | run natively on the ARM build runner |
| agentbrowser-mcp-windows-x64.exe | run natively on the build runner |
The CLI (agentbrowser-cli-<target>) ships from this release too —
--version and --help smoke-tested wherever the runner can execute it (same
targets/omissions as the MCP binary).
Each smoke ran initialize + tools/list against the compiled
artifact and required the complete unbound catalog and the exact release version
in serverInfo.
Server acceptance uses Node 24.21.0 on native Linux x64/ARM and Darwin ARM.
The Darwin x64 tarball is exercised on ARM Node with Rosetta x64 clients;
this is not native Intel server-runtime proof. The Windows bundle was
assembled and smoke-tested on a hosted Windows runner from a clean room
outside the build checkout: first start, a real Chromium session through
the CLI and MCP executables, launcher-kill cleanup, invocation through
a symlink (winget's Links directory), and a first start that downloads
Chromium itself.
Install
# verify against sha256sums.txt after download
chmod +x agentbrowser-mcp-<target># ~/.victor/mcp.yaml - no Node, no repo checkout
mcpServers:
agentbrowser:
command: /usr/local/bin/agentbrowser-mcp
env:
AGENTBROWSER_BASE_URL: http://localhost:5709Built with bun 1.4.0.
v1.19.0
AgentBrowser v1.19.0
AgentBrowser ships a first-class CLI, a service and an optional MCP
adapter. Point the CLI at a reachable service with --base-url, or set
AGENTBROWSER_BASE_URL for MCP (default http://localhost:5709). The MCP
executable is only the stdio adapter, not the service.
See the versioned changelog
for included capabilities and qualification limits.
The service is now installable too: agentbrowser-server-<target>.tar.gz
is a self-contained server build (pruned production node_modules +
compiled dist/) whose every artifact passed extracted-package acceptance:
real Chromium navigation/snapshot/action, valid screenshot/PDF bytes,
HTTP/TLS downloads, denial/cancellation controls and matching CLI/MCP calls.
Stock-launcher default denial and instrumented snapshot recovery are
distinct checks. This is not hostile-browser containment evidence.
tar -xzf agentbrowser-server-<target>.tar.gz && ./server/agentbrowser-server
# needs Node 22 or newer plus a compatible Chromium already installed under
# PLAYWRIGHT_BROWSERS_PATH; the archive launcher does not download it.
# Linux hosts must also provide Chromium's platform libraries.Homebrew users get the server, CLI and MCP in one command:
brew install anvai-labs/tap/agentbrowser
(brew services start anvai-labs/tap/agentbrowser runs the service).
Windows users get all three in agentbrowser-windows-x64.zip
(winget install AnvaiLabs.AgentBrowser, or extract the zip anywhere):
agentbrowser-server.exe runs the service on the bundled Node.js
runtime (node\) and downloads its Chromium on first start
(--install-browser pre-provisions it).
agentbrowser-server --version
agentbrowser-server # first start downloads Chromium (~300 MB)Smoke coverage
| Artifact | Stdio smoke |
|---|---|
| agentbrowser-mcp-darwin-arm64 | run natively on the build runner |
| agentbrowser-mcp-darwin-x64 | run via Rosetta on the arm64 runner |
| agentbrowser-mcp-linux-x64 | run natively on the build runner |
| agentbrowser-mcp-linux-arm64 | run natively on the ARM build runner |
| agentbrowser-mcp-windows-x64.exe | run natively on the build runner |
The CLI (agentbrowser-cli-<target>) ships from this release too —
--version and --help smoke-tested wherever the runner can execute it (same
targets/omissions as the MCP binary).
Each smoke ran initialize + tools/list against the compiled
artifact and required the complete unbound catalog and the exact release version
in serverInfo.
Server acceptance uses Node 24.21.0 on native Linux x64/ARM and Darwin ARM.
The Darwin x64 tarball is exercised on ARM Node with Rosetta x64 clients;
this is not native Intel server-runtime proof. The Windows bundle was
assembled and smoke-tested on a hosted Windows runner from a clean room
outside the build checkout: first start, a real Chromium session through
the CLI and MCP executables, launcher-kill cleanup, invocation through
a symlink (winget's Links directory), and a first start that downloads
Chromium itself.
Install
# verify against sha256sums.txt after download
chmod +x agentbrowser-mcp-<target># ~/.victor/mcp.yaml - no Node, no repo checkout
mcpServers:
agentbrowser:
command: /usr/local/bin/agentbrowser-mcp
env:
AGENTBROWSER_BASE_URL: http://localhost:5709Built with bun 1.4.0.