Distribution

ABG release artifacts are built from the repository and published for the app, CLI, and browser extension through GitHub Releases.

Current public distribution state:

• macOS app: signed and notarized v0.4.8 DMG on GitHub Releases
• Chrome extension: v0.4.4 on the Chrome Web Store, updated August 21, 2026
• Windows package: pending signed release and WinGet indexing

The app and extension versions can differ while Chrome Web Store review and signed app publication complete independently.

Homebrew cask

The macOS cask installs:

• Agent Browser Gateway.app into /Applications
• abg into Homebrew’s bin

Install test:

brew tap arcmanagement/agent-browser-gateway https://github.com/arcmanagement/agent-browser-gateway
brew trust --cask arcmanagement/agent-browser-gateway/agent-browser-gateway
brew install --cask agent-browser-gateway

If Homebrew reports that the latest version is already installed, the cask install path is working and no update is needed.

Homebrew is ready for a release when the versioned macOS ZIP is published under the matching GitHub Release, and this repository’s Casks/agent-browser-gateway.rb points at that version and SHA-256.

Chrome Web Store

Install the extension from the public Chrome Web Store listing.

For release verification, confirm that the public listing is available, then record its displayed version and update date separately from the latest macOS release. The current listing reports version 0.4.4, updated August 21, 2026.

WinGet

The Windows package identifier is:

winget install --id ArcManagement.AgentBrowserGateway --source winget

Current v0.4.8 status: this package is not indexed yet, and the command above returns no matching package until the signed Windows release workflow and WinGet submission are completed.

WinGet is ready for a release after the public Windows setup ZIP is available from GitHub Releases and the generated microsoft/winget-pkgs PR is merged and indexed.

Signed local release build

Maintainer release builds are created on a trusted Mac:

export VERSION=0.4.8
make dist VERSION="$VERSION" \
  SIGN_IDENTITY="Developer ID Application: ArcManagement Inc (M46W5MVAQP)" \
  NOTARY_PROFILE="abg-notary"

Keep Developer ID signing local. Do not put the Developer ID private key, certificate password, App Store Connect credentials, or notarytool credentials into GitHub Actions secrets.

Reproducible build and release trust

Before a v1.0 release, maintainers can run the unsigned reproducible dry run:

make reproducible-build

The dry run writes extension and Gateway comparison artifacts, SHA256SUMS.txt, BUILD_INPUTS.txt, and agent-browser-gateway-$VERSION.spdx.json under dist/reproducible-build/. The full checksum, signing, SBOM, provenance, and user verification plan is tracked in docs/RELEASE_ARTIFACT_TRUST.md.

Verify artifacts

codesign --verify --strict --verbose=2 \
  "dist/agent-browser-gateway-$VERSION-macos-arm64/Agent Browser Gateway.app"
codesign --verify --strict --verbose=2 \
  "dist/agent-browser-gateway-$VERSION-macos-arm64/abg"
spctl --assess --type execute --verbose \
  "dist/agent-browser-gateway-$VERSION-macos-arm64/Agent Browser Gateway.app"
shasum -a 256 \
  "dist/agent-browser-gateway-$VERSION-macos-arm64.zip" \
  "dist/agent-browser-gateway-extension-$VERSION.zip"

CI may build and test unsigned artifacts. Signed release assets should be created on a trusted maintainer Mac and uploaded to the draft GitHub Release before publication.

Users who download a direct artifact should also download the matching checksum file and verify it before installation:

shasum -a 256 -c agent-browser-gateway-$VERSION-macos-arm64.dmg.sha256.txt

Mac App Store

The Mac App Store path is separate from the Developer ID and Homebrew release path. Store builds must use App Sandbox and App Store distribution signing, then be uploaded to App Store Connect.

The working checklist lives in docs/app-store-submission.md.