Skip to content

Agent Browser v0.2.1 - evidence-coherent patch release

Choose a tag to compare

View all tags
@AetherAI3 AetherAI3 released this 04 Sep 10:26
· 7 commits to main since this release
v0.2.1
92b6868
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.1 is a release-integrity and public-documentation patch for the first MCP-capable
stable line. It makes the tagged source archive, evidence record, and manifest-closure sequence
coherent without moving or rewriting the published v0.2.0 tag.

What changed

  • Bumped the runtime, source-built image, Compose service, Node client, Python client, MCP server
    metadata, and CLI source tag to 0.2.1.
  • Replaced stale v0.1 release-candidate launch copy with current Node, Python, npm, PyPI, and MCP
    guidance.
  • Reconciled the demo record: the current recorded demonstration and superseded v0.1 still montage
    are clearly separated, current asset checksums are published, and the limits of the retained
    capture provenance are explicit.
  • Corrected the release record so hosted runtime evidence is not misattributed to the separate demo
    capture or to evidence-only files excluded from the container build context.
  • Closed the release in three deliberate stages before tagging: reviewed runtime, evidence rebind,
    and generated-manifest commit.

No route, request model, authorization boundary, listener default, runtime dependency, or
distribution permission changed in this patch. The API remains api_version: "v1".

Install and connect

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

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

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

docker compose up --build

Exact release evidence

  • Runtime commit: 38cc23f281001a9d678642916da522c047f9151d
  • Evidence commit: 7acde1c493d2a2595554c012d1091f8371d3439d
  • Tagged manifest-closure commit: 92b686861ea9aa4ec78f5345fe873c213e158810
  • 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.

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.

Historical correction

The v0.2.0 package provenance remains valid for its immutable tag, but that source tag was created
before its later evidence-rebind and manifest commits. v0.2.1 preserves the old tag and supersedes
that evidence-packaging order with a tag created only after closure. Use v0.2.1 for the coherent
source-and-evidence release record.

Assets 3
Loading