Skip to content

Agent Browser v0.2.2 - MCP Registry publication release

Latest
Latest

Choose a tag to compare

View all tags
@AetherAI3 AetherAI3 released this 04 Sep 11:35
· 4 commits to main since this release
v0.2.2
9981040
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Agent Browser v0.2.2 makes the project publishable to the official MCP Registry as
io.github.AetherAI3/agent-browser. It adds publication metadata and nothing else: no route,
request model, authorization boundary, listener default, runtime dependency, or distribution
permission changed. The API remains api_version: "v1".

What changed

  • Added server.json at the repository root, describing both clients — the npm and PyPI
    aether-browser packages — each started as aether-browser mcp over stdio, with
    AGENT_BROWSER_URL, AGENT_BROWSER_CONTROLLER_TOKEN, and AGENT_BROWSER_OBSERVER_TOKEN
    declared as optional environment variables.
  • Added the ownership proofs the registry verifies against live package metadata: an mcpName
    field in the npm client's package.json, and an mcp-name marker at the top of the PyPI
    client's README, which is that package's long description.
  • Bumped the runtime, source-built image, Compose service, Node client, Python client, MCP server
    metadata, and CLI source tag to 0.2.2.

v0.2.1 could not carry those markers: both of its artifacts were already published, and neither npm
nor PyPI allows a published version to be replaced.

Install and connect

npm install aether-browser@0.2.2
pip install aether-browser==0.2.2

# Serve the same nine Agent Browser tools to an MCP client:
npx -y aether-browser@0.2.2 mcp
aether-browser mcp

The self-hosted Linux runtime still starts from source with:

docker compose up --build

Exact release evidence

  • Runtime commit: 648269bf4ec5da534f2a4afe81104ab52c826bb3
  • Evidence commit: 85ec2a6de4e971c6e77eab83e508c090c8f0b1f6
  • Tagged manifest-closure commit: 9981040b2e873b4120d0bc57850cbbb917603708
  • Final exact-tag release-evidence run: all five jobs passed, including the fresh Compose quickstart, rootless image build, 33-check isolated acceptance, and strict release-integrity gate.
  • Exact-main CI run: passed.
  • The committed release/evidence/manifest.json attests the evidence commit. The attached release-evidence.json asset attests the exact tagged commit; it cannot be embedded in that same commit without changing the commit SHA.

Both published packages carry npm provenance and PyPI Trusted Publishing attestations from those
runs.

The release remains source-only. No Chrome-containing image, image tar, filesystem layer, or public
layer cache is attached. Chrome inventory, vulnerability scan posture, third-party notices, host
qualification scope, and demo limits are recorded in the tag-pinned
RELEASE_EVIDENCE.md
and DEMO_EVIDENCE.md.

Assets 3
Loading