Skip to content

v1.9.0

Choose a tag to compare

@github-actions github-actions released this 19 Sep 10:39
· 660 commits to main since this release
02f263f

1.9.0 foundation checkpoint

T2 is complete: shared execution and verification now include business receipt correlation, scoped receipt preflight, pending-read admission drain, and generation-fenced evidence permission. CLI/SDK/REST use the shared service; MCP remains optional. The controlled G4 fixture qualifies seven compiled-CLI cases and reconciled replays. Production evidence/G6, durable recovery and the user-facing T3 QA reporting vertical remain follow-up work.

Published from protected main commit 02f263f3764b41f923553c69c11dff69c819fae5 after independent adversarial review, eight green promotion checks, eight green main checks and all twelve release jobs. All fourteen downloaded artifacts matched sha256sums.txt; the published Darwin ARM64 service and matching clients passed all eight real-browser acceptance groups on Node 22.23.2. The exact npm package's SHA-512 and MCP version/catalog smoke also passed. These checks do not claim an upgrade of an existing user installation or a managed-service restart.

See the 1.9.0 changelog for behavior and qualification limits.

AgentBrowser v1.9.0

AgentBrowser ships a first-class CLI, a service and an optional MCP
adapter. Point either client at a reachable AgentBrowser service via
AGENTBROWSER_BASE_URL (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 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).

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 full 13-tool unbound catalog and the exact release version
in serverInfo.

Server acceptance uses Node 22 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. Windows has executable
acceptance only: no Windows server tarball is shipped.

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:5709

Built with bun 1.4.0.