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: list and attest install.sh too
Kyle Elliott19985e141951
diff --git a/.github/workflows/release.yml b/.github/workflows/release.ymlindex f5d0bca6..dd6aab99 100644--- a/.github/workflows/release.yml+++ b/.github/workflows/release.yml@@ -9,7 +9,7 @@ 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+# 4. finalize — (after all three) adds the .pkg, .msi and install.sh to checksums.txt and# records a GitHub build-provenance attestation for every file# checksums.txt lists.#@@ -426,15 +426,17 @@ jobs:TAG: ${{ github.ref_name }}GH_TOKEN: ${{ github.token }}steps:- - name: Add the .pkg and .msi to checksums.txt+ - name: Add the .pkg, .msi and install.sh to checksums.txtrun: |set -euo pipefailmkdir -p dist/release && cd dist/releasegh release download "$TAG" --repo "$REPO" --pattern checksums.txt- for pattern in 'BeaconEndpointAgent-*.pkg' 'BeaconEndpointAgent-*.msi'; do+ # install.sh is what `curl -fsSL https://beacon.sh/install.sh | bash` runs (beacon.sh+ # redirects to this release's copy), so it is attested like the packages it installs.+ for pattern in 'BeaconEndpointAgent-*.pkg' 'BeaconEndpointAgent-*.msi' 'install.sh'; dogh release download "$TAG" --repo "$REPO" --pattern "$pattern" || echo "::warning::no $pattern on the release"done- for f in BeaconEndpointAgent-*.pkg BeaconEndpointAgent-*.msi; do+ for f in BeaconEndpointAgent-*.pkg BeaconEndpointAgent-*.msi install.sh; 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 || continuediff --git a/CLAUDE.md b/CLAUDE.mdindex 2e5b8ac9..1f5e4c3d 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -283,7 +283,7 @@ A pushed `v*` tag runs the full release end-to-end via`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+ appends the `.pkg`, `.msi` and `install.sh` to `checksums.txt` from the released bytes andrecords a GitHub build-provenance attestation (Sigstore, keyless, through theworkflow's OIDC token) for every file `checksums.txt` lists. It needs`id-token: write` and `attestations: write` and no `release`-environment secrets.@@ -392,7 +392,7 @@ 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`. `checksums.txt` lists-the archives, the Linux packages, the `.pkg` and the `.msi`, and each of those has a+the archives, the Linux packages, the `.pkg`, the `.msi` and `install.sh`, and each of those has abuild-provenance attestation.The MSI is unsigned, so `pkgutil`/`stapler`/`spctl` have no Windows counterpart todiff --git a/docs/changelog/cli.mdx b/docs/changelog/cli.mdxindex 113833c9..52057d35 100644--- a/docs/changelog/cli.mdx+++ b/docs/changelog/cli.mdx@@ -13,7 +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.+- **Release downloads can be verified end to end** · Every archive, Linux package, macOS `.pkg`, Windows `.msi` and the Linux `install.sh` 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`, `.msi` and `install.sh`. 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, 2026