The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu
Go agent-ai-cliagent-harnessesagent-securitybrowser-extensionciclaude-codecloudcodexcursordetection-engineeringjevknowledge-basememorymobile-device-managementobservabilitysecuritysecurity-information-and-event-managementsecurity-toolstelemetrytraces
release: attest every artifact, list .pkg/.msi in checksums.txt, fix sidecars, pin actions
Kyle Elliott36aa124e61bb
diff --git a/.github/workflows/release-extension.yml b/.github/workflows/release-extension.ymlindex ac4355d5..d0ee120b 100644--- a/.github/workflows/release-extension.yml+++ b/.github/workflows/release-extension.yml@@ -52,8 +52,8 @@ jobs:REPO: ${{ github.repository }}TAG: ${{ github.ref_name }}steps:- - uses: actions/checkout@v4- - uses: actions/setup-node@v4+ - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4.4.0+ - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0with:node-version: 22cache: npm@@ -256,9 +256,9 @@ jobs:fiecho "sign=true" >> "$GITHUB_OUTPUT"- - uses: actions/checkout@v4+ - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4.4.0if: steps.gate.outputs.sign == 'true'- - uses: actions/setup-node@v4+ - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0if: steps.gate.outputs.sign == 'true'with:node-version: 22diff --git a/.github/workflows/release.yml b/.github/workflows/release.ymlindex 3751b704..f5d0bca6 100644--- a/.github/workflows/release.yml+++ b/.github/workflows/release.yml@@ -9,6 +9,9 @@ name: Release# 3. windows-package — (after goreleaser) builds the Windows MSI from the archive# goreleaser just published, installs it to prove it works, and# attaches it. Unsigned for now, so it needs no secrets.+# 4. finalize — (after all three) adds the .pkg and .msi to checksums.txt and+# records a GitHub build-provenance attestation for every file+# checksums.txt lists.## Triggered only by pushed version tags, so outside contributors (whose fork PRs# never receive secrets) cannot run it. All release secrets live in the protected@@ -27,15 +30,15 @@ jobs:runs-on: ubuntu-latestenvironment: releasesteps:- - uses: actions/checkout@v4+ - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4.4.0with:fetch-depth: 0- - uses: actions/setup-go@v5+ - uses: actions/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff # v5.6.0with:go-version-file: cli/beacon/go.mod- - uses: goreleaser/goreleaser-action@v6+ - uses: goreleaser/goreleaser-action@e435ccd777264be153ace6237001ef4d979d3a7a # v6.4.0with:version: "v2.13.3"install-only: true@@ -96,11 +99,11 @@ jobs:BEACON_PKG_ARCHES: "arm64"VECTOR_VERSION: "0.56.0"steps:- - uses: actions/checkout@v4+ - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4.4.0with:fetch-depth: 0- - uses: actions/setup-go@v5+ - uses: actions/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff # v5.6.0with:go-version-file: cli/beacon/go.mod@@ -322,7 +325,7 @@ jobs:run:shell: pwshsteps:- - uses: actions/checkout@v4+ - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4.4.0- name: Fetch the published Windows archiveenv:@@ -399,3 +402,56 @@ jobs:$ErrorActionPreference = 'Stop'& gh release upload $env:TAG (Get-ChildItem dist\windows -Filter '*.msi').FullName (Get-ChildItem dist\windows -Filter '*.msi.sha256').FullName --repo $env:REPO --clobberif ($LASTEXITCODE -ne 0) { throw "uploading the MSI failed" }++ # One checksums.txt for everything a user installs, and signed provenance for all of it.+ #+ # goreleaser writes checksums.txt before the .pkg and .msi exist, so they are appended here from the+ # bytes on the release. The attestation is a Sigstore-signed statement, made with this workflow's+ # OIDC identity, that this repository's release workflow built each file at this tag; anyone can+ # check a download with `gh attestation verify <file> --repo Asymptote-Labs/agent-beacon`. Unlike+ # checksums.txt, it cannot be replaced by someone who can only edit the release.+ #+ # Runs when goreleaser succeeded even if a packaging job failed, so the archives and Linux packages+ # are still covered; a missing .pkg or .msi is simply not appended.+ finalize:+ needs: [goreleaser, package, windows-package]+ if: ${{ !cancelled() && needs.goreleaser.result == 'success' }}+ runs-on: ubuntu-latest+ permissions:+ contents: write+ id-token: write+ attestations: write+ env:+ REPO: ${{ github.repository }}+ TAG: ${{ github.ref_name }}+ GH_TOKEN: ${{ github.token }}+ steps:+ - name: Add the .pkg and .msi to checksums.txt+ run: |+ set -euo pipefail+ mkdir -p dist/release && cd dist/release+ gh release download "$TAG" --repo "$REPO" --pattern checksums.txt+ for pattern in 'BeaconEndpointAgent-*.pkg' 'BeaconEndpointAgent-*.msi'; do+ gh release download "$TAG" --repo "$REPO" --pattern "$pattern" || echo "::warning::no $pattern on the release"+ done+ for f in BeaconEndpointAgent-*.pkg BeaconEndpointAgent-*.msi; do+ [ -f "$f" ] || continue+ # A rerun must not list a file twice: install.sh refuses a name with two checksums.+ awk -v name="$f" '$2 == name { found = 1 } END { exit found }' checksums.txt || continue+ sha256sum "$f" >> checksums.txt+ done+ sha256sum --check checksums.txt --ignore-missing+ gh release upload "$TAG" checksums.txt --repo "$REPO" --clobber++ - name: Download every file checksums.txt lists+ working-directory: dist/release+ run: |+ set -euo pipefail+ awk '{ print $2 }' checksums.txt | while read -r name; do+ [ -f "$name" ] || gh release download "$TAG" --repo "$REPO" --pattern "$name"+ done+ sha256sum --check --strict checksums.txt++ - uses: actions/attest-build-provenance@4d101475d8b20a2381f78447822ac1eab6504dd8 # v4.2.2+ with:+ subject-checksums: dist/release/checksums.txtdiff --git a/CLAUDE.md b/CLAUDE.mdindex 74c12565..2e5b8ac9 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -266,7 +266,7 @@ local GoReleaser publish only as a fallback when CI release automation is notavailable or the maintainer explicitly asks for a local release.A pushed `v*` tag runs the full release end-to-end via-`.github/workflows/release.yml` (no local publish steps required), in three jobs:+`.github/workflows/release.yml` (no local publish steps required), in four jobs:1. `goreleaser` (ubuntu, `environment: release`) builds the collector dists,publishes the GitHub release + changelog and tarballs, and updates the@@ -282,6 +282,15 @@ A pushed `v*` tag runs the full release end-to-end viaworks, and attaches the `.msi` and its `.sha256`. Deliberately **not** in the`release` environment: that environment gates signing secrets, and the MSI isunsigned, so this job has none to gate.+4. `finalize` (ubuntu, `needs` all three, runs whenever `goreleaser` succeeded)+ appends the `.pkg` and `.msi` to `checksums.txt` from the released bytes and+ records a GitHub build-provenance attestation (Sigstore, keyless, through the+ workflow's OIDC token) for every file `checksums.txt` lists. It needs+ `id-token: write` and `attestations: write` and no `release`-environment secrets.++Every third-party action in `release.yml` and `release-extension.yml` is pinned to+a full commit SHA with the version in a trailing comment, because these jobs hold+the signing secrets. Bump them by SHA, never back to a tag.Required `release`-environment secrets: `HOMEBREW_TAP_TOKEN`,`DEVELOPER_ID_APP_CERT_P12`, `DEVELOPER_ID_APP_CERT_PASSWORD`,@@ -382,7 +391,9 @@ docker run --rm --platform linux/amd64 homebrew/brew sh -c \The release should include the five GoReleaser CLI archives (four `.tar.gz` plus`beacon_<version>_windows_amd64.zip`), `checksums.txt`, `threat-rules.tar.gz`, `install.sh` (the Linux one-line installer from `packaging/linux/install.sh`),`BeaconEndpointAgent-<version>-arm64.pkg`, its `.sha256`, `update-manifest.json`,-and `BeaconEndpointAgent-<version>-x64.msi` with its `.sha256`.+and `BeaconEndpointAgent-<version>-x64.msi` with its `.sha256`. `checksums.txt` lists+the archives, the Linux packages, the `.pkg` and the `.msi`, and each of those has a+build-provenance attestation.The MSI is unsigned, so `pkgutil`/`stapler`/`spctl` have no Windows counterpart torun. Its `.sha256` is therefore the only integrity check it has, and the release@@ -394,9 +405,8 @@ signing is added. Verify the package before announcing the release:tmpdir="$(mktemp -d)"cd "$tmpdir"gh release download <tag> --repo Asymptote-Labs/agent-beacon --pattern 'BeaconEndpointAgent-*-arm64.pkg*' --pattern update-manifest.json-expected="$(awk '{print $1}' BeaconEndpointAgent-*-arm64.pkg.sha256)"-actual="$(shasum -a 256 BeaconEndpointAgent-*-arm64.pkg | awk '{print $1}')"-test "$expected" = "$actual"+shasum -a 256 -c BeaconEndpointAgent-*-arm64.pkg.sha256+gh attestation verify BeaconEndpointAgent-*-arm64.pkg --repo Asymptote-Labs/agent-beaconpkgutil --check-signature BeaconEndpointAgent-*-arm64.pkgxcrun stapler validate BeaconEndpointAgent-*-arm64.pkgspctl --assess --type install -vv BeaconEndpointAgent-*-arm64.pkgdiff --git a/README.md b/README.mdindex af033259..dc4b59e5 100644--- a/README.md+++ b/README.md@@ -112,7 +112,7 @@ grep " ${PKG}$" checksums.txt | sha256sum --check - && \sudo apt install "./${PKG}" # or: sudo dnf install "./${PKG}"```-`checksums.txt` is published with the release, so it catches a corrupted or swapped download but does not prove who built the release. If that matters to you, pin `VERSION` to a release you have reviewed instead of following `latest`. To install without root, use the tarball in user mode ([Linux install guide](https://docs.asymptotelabs.ai/platforms/linux#without-root-or-without-a-package-manager)).+`checksums.txt` is published with the release, so it catches a corrupted or swapped download but does not prove who built the release. To check that, verify the package's build-provenance attestation, which shows it was built by this repository's release workflow: `gh attestation verify "${PKG}" --repo asymptote-labs/agent-beacon`. You can also pin `VERSION` to a release you have reviewed instead of following `latest`. To install without root, use the tarball in user mode ([Linux install guide](https://docs.asymptotelabs.ai/platforms/linux#without-root-or-without-a-package-manager)).</details>diff --git a/docs/changelog/cli.mdx b/docs/changelog/cli.mdxindex 6246bfba..113833c9 100644--- a/docs/changelog/cli.mdx+++ b/docs/changelog/cli.mdx@@ -13,6 +13,7 @@ Stay up to date with the latest changes to the Agent Beacon CLI.- **The scheduled inventory job follows every moved runtime directory** · The job starts without your shell's environment, so a per-user install or repair records the variables that move a runtime's user directory into it. It recorded `CODEX_HOME`, `HERMES_HOME`, `CLINE_DIR`, `GEMINI_CLI_HOME` and `CLAUDE_CONFIG_DIR`, and now also `KIRO_HOME`, `KIMI_CODE_HOME`, `DSH_HOME`, `OH_PERSISTENCE_DIR`, `OPENCLAW_STATE_DIR`, `XDG_CONFIG_HOME` (Muse, and VS Code on Linux), `PI_CODING_AGENT_DIR`, `OMO_CODING_AGENT_DIR`, `SENPI_CODING_AGENT_DIR`, `PRIME_AGENT_CODING_AGENT_DIR`, and Oh My Pi's `PI_CONFIG_DIR`, `OMP_PROFILE` and `PI_PROFILE`. With one of these set only in your shell, the job used to inventory the default directory while the runtime read the moved one. See [Inventory heartbeats](/cli/endpoint-inventory#inventory-heartbeats).- **Pi extension follows `PI_CODING_AGENT_DIR`** · `beacon endpoint hooks install --harness pi`, `beacon endpoint discover` and inventory now use `$PI_CODING_AGENT_DIR/extensions/beacon.ts` when `PI_CODING_AGENT_DIR` is set, as Pi does, including a leading `~`. They previously always used `~/.pi/agent`, so with the variable set the extension went where Pi never loads it while discovery reported Pi as enabled, and live capture silently recorded nothing. Session status and sync already followed the variable; all of them now resolve the directory the same way.+- **Release downloads can be verified end to end** · Every archive, Linux package, macOS `.pkg` and Windows `.msi` on a release now has a GitHub build-provenance attestation, so `gh attestation verify <file> --repo asymptote-labs/agent-beacon` confirms it was built by this repository's release workflow, which a checksum published beside the file cannot prove. `checksums.txt` now also lists the `.pkg` and `.msi`. The `.pkg.sha256` and `.msi.sha256` files work with `shasum -a 256 -c` and `sha256sum -c`: the first named the build machine's path and the second ended in a Windows line ending, so both checks reported the file missing.### v1.3.42 · October 15, 2026diff --git a/packaging/macos/build-pkg.sh b/packaging/macos/build-pkg.shindex 19fb438d..0e1e36f9 100755--- a/packaging/macos/build-pkg.sh+++ b/packaging/macos/build-pkg.sh@@ -152,5 +152,7 @@ if [ -n "${NOTARYTOOL_PROFILE:-}" ]; thenxcrun stapler staple "$PKG_PATH"fi-shasum -a 256 "$PKG_PATH" > "$PKG_PATH.sha256"+# Hash from the package's directory so the sidecar names the file, not this machine's path, and+# `shasum -a 256 -c` works beside the downloaded package.+(cd "$(dirname "$PKG_PATH")" && shasum -a 256 "$(basename "$PKG_PATH")") > "$PKG_PATH.sha256"echo "$PKG_PATH"diff --git a/packaging/macos/build-signed-notarized-pkg.sh b/packaging/macos/build-signed-notarized-pkg.shindex 3621d2fb..61ccb219 100755--- a/packaging/macos/build-signed-notarized-pkg.sh+++ b/packaging/macos/build-signed-notarized-pkg.sh@@ -118,6 +118,6 @@ if [ "$SKIP_VERIFY" -eq 0 ]; thenspctl -a -vv -t install "$PKG_PATH"fi-shasum -a 256 "$PKG_PATH" > "$PKG_PATH.sha256"+(cd "$(dirname "$PKG_PATH")" && shasum -a 256 "$(basename "$PKG_PATH")") > "$PKG_PATH.sha256"echo "signed and notarized package: $PKG_PATH"echo "checksum: $PKG_PATH.sha256"diff --git a/packaging/windows/build-msi.ps1 b/packaging/windows/build-msi.ps1index 68db849c..90c2815c 100644--- a/packaging/windows/build-msi.ps1+++ b/packaging/windows/build-msi.ps1@@ -79,7 +79,9 @@ try {# only integrity check available on an unsigned artifact, and it stays mandatory once signing is# added rather than being replaced by it.$hash = (Get-FileHash -LiteralPath $OutFile -Algorithm SHA256).Hash.ToLower()- "$hash $(Split-Path -Leaf $OutFile)" | Set-Content -LiteralPath "$OutFile.sha256" -Encoding ascii+ # LF, not Set-Content's CRLF: with a trailing CR, `shasum -c` and `sha256sum -c` on macOS and+ # Linux look for a file whose name ends in \r and report it missing.+ "$hash $(Split-Path -Leaf $OutFile)`n" | Set-Content -LiteralPath "$OutFile.sha256" -Encoding ascii -NoNewlineWrite-Output "sha256: $hash"Write-Output $OutFile} finally {