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
docs: resolve the release and architecture in the copy-paste install commands
Claude78d0a9db4b45
diff --git a/docs/cli/manual-install.mdx b/docs/cli/manual-install.mdxindex 7ef929b4..b25b50ff 100644--- a/docs/cli/manual-install.mdx+++ b/docs/cli/manual-install.mdx@@ -14,21 +14,45 @@ All three matter. `beacon-hooks` is what supported runtimes invoke to record proand approvals, so an install that keeps only the CLI and the collector captures OpenTelemetry dataand nothing from the hook path.-```bash title="Download, verify, and extract (Linux amd64)"-VERSION=1.2.0 # or whichever release you are installing-BASE=https://github.com/asymptote-labs/agent-beacon/releases/download/v${VERSION}-curl -fsSLO ${BASE}/beacon_${VERSION}_linux_amd64.tar.gz-curl -fsSLO ${BASE}/checksums.txt-sha256sum --check --ignore-missing checksums.txt--tar -xzf beacon_${VERSION}_linux_amd64.tar.gz+```bash title="Download, verify, and extract (macOS or Linux)"+LATEST_URL="$(curl -fsSLI -o /dev/null -w '%{url_effective}' https://github.com/asymptote-labs/agent-beacon/releases/latest)"+VERSION="${LATEST_URL##*/v}"++case "$(uname -s)" in+ Linux) OS=linux ;;+ Darwin) OS=darwin ;;+ *) echo "Beacon publishes macOS and Linux archives, not $(uname -s)" >&2; exit 1 ;;+esac++case "$(uname -m)" in+ x86_64) ARCH=amd64 ;;+ aarch64|arm64) ARCH=arm64 ;;+ *) echo "Beacon publishes amd64 and arm64 archives, not $(uname -m)" >&2; exit 1 ;;+esac++ARCHIVE="beacon_${VERSION}_${OS}_${ARCH}.tar.gz"+BASE="https://github.com/asymptote-labs/agent-beacon/releases/download/v${VERSION}"+curl -fsSLO "${BASE}/${ARCHIVE}"+curl -fsSLO "${BASE}/checksums.txt"++# Verify this exact archive before extracting it. macOS ships shasum rather than sha256sum.+if [ "$OS" = darwin ]; then+ grep " ${ARCHIVE}$" checksums.txt | shasum -a 256 -c -+else+ grep " ${ARCHIVE}$" checksums.txt | sha256sum --check -+fi++tar -xzf "${ARCHIVE}"mkdir -p ~/.local/bin && mv beacon beacon-hooks beacon-otelcol ~/.local/bin/beacon version```-Swap `linux_amd64` for `linux_arm64`, `darwin_arm64`, or `darwin_amd64` as needed; on macOS use-`shasum -a 256 -c` in place of `sha256sum --check`. The archive layout is identical across-platforms.+The version comes from the current release rather than a number to keep up to date, and the+platform and architecture come from `uname`: `x86_64` maps to the published `amd64` archive and+`aarch64` to `arm64`. A platform or architecture Beacon does not publish stops the run before+anything is downloaded. The checksum step names the one archive about to be extracted, so it+verifies that file rather than whatever else the directory happens to hold. The archive layout is+identical across platforms.For managed endpoint rollouts on Apple Silicon Macs, GitHub Releases also attacha signed, notarized, and stapled `BeaconEndpointAgent-<version>-arm64.pkg`. Thediff --git a/docs/get-started/quickstart-developers.mdx b/docs/get-started/quickstart-developers.mdxindex 589a5054..5299b5e4 100644--- a/docs/get-started/quickstart-developers.mdx+++ b/docs/get-started/quickstart-developers.mdx@@ -17,12 +17,23 @@ beacon endpoint install``````bash title="Linux"-VERSION=1.2.0 # or whichever release you are installing-curl -fsSLO https://github.com/asymptote-labs/agent-beacon/releases/download/v${VERSION}/beacon_${VERSION}_linux_amd64.tar.gz-curl -fsSLO https://github.com/asymptote-labs/agent-beacon/releases/download/v${VERSION}/checksums.txt-sha256sum --check --ignore-missing checksums.txt+LATEST_URL="$(curl -fsSLI -o /dev/null -w '%{url_effective}' https://github.com/asymptote-labs/agent-beacon/releases/latest)"+VERSION="${LATEST_URL##*/v}"-tar -xzf beacon_${VERSION}_linux_amd64.tar.gz+case "$(uname -m)" in+ x86_64) ARCH=amd64 ;;+ aarch64|arm64) ARCH=arm64 ;;+ *) echo "Beacon publishes Linux archives for amd64 and arm64, not $(uname -m)" >&2; exit 1 ;;+esac++ARCHIVE="beacon_${VERSION}_linux_${ARCH}.tar.gz"+BASE="https://github.com/asymptote-labs/agent-beacon/releases/download/v${VERSION}"+curl -fsSLO "${BASE}/${ARCHIVE}"+curl -fsSLO "${BASE}/checksums.txt"++grep " ${ARCHIVE}$" checksums.txt | sha256sum --check -++tar -xzf "${ARCHIVE}"mkdir -p ~/.local/bin && mv beacon beacon-hooks beacon-otelcol ~/.local/bin/beacon endpoint install```@@ -35,6 +46,12 @@ beacon endpoint installlog. If you want the system-mode package, follow [Linux](/platforms/linux) instead of this page.</Note>+The Linux commands resolve the current release rather than a version you have to edit in, map+`x86_64` and `aarch64` to the archive names Beacon actually publishes, and stop before downloading+anything on an architecture with no published archive. The checksum step names the one archive+about to be extracted, so it verifies that file rather than whatever else the directory happens to+hold.+See [Asymptote Open Source](/deployment/open-source) for install details and runtime-specific notes,or [macOS](/platforms/macos), [Linux](/platforms/linux), or [Windows](/platforms/windows) for theplatform detail.diff --git a/docs/platforms/linux.mdx b/docs/platforms/linux.mdxindex f2209220..235f12c2 100644--- a/docs/platforms/linux.mdx+++ b/docs/platforms/linux.mdx@@ -34,14 +34,24 @@ If you are not an administrator on the machine, or you would rather not touch sytarball and install in user mode:```bash title="Tarball install, no root required"-VERSION=1.2.0 # or whichever release you are installing-curl -fsSLO https://github.com/asymptote-labs/agent-beacon/releases/download/v${VERSION}/beacon_${VERSION}_linux_amd64.tar.gz-curl -fsSLO https://github.com/asymptote-labs/agent-beacon/releases/download/v${VERSION}/checksums.txt+LATEST_URL="$(curl -fsSLI -o /dev/null -w '%{url_effective}' https://github.com/asymptote-labs/agent-beacon/releases/latest)"+VERSION="${LATEST_URL##*/v}"-# Verify before extracting. This is the integrity check for the tarball.-sha256sum --check --ignore-missing checksums.txt+case "$(uname -m)" in+ x86_64) ARCH=amd64 ;;+ aarch64|arm64) ARCH=arm64 ;;+ *) echo "Beacon publishes Linux archives for amd64 and arm64, not $(uname -m)" >&2; exit 1 ;;+esac-tar -xzf beacon_${VERSION}_linux_amd64.tar.gz+ARCHIVE="beacon_${VERSION}_linux_${ARCH}.tar.gz"+BASE="https://github.com/asymptote-labs/agent-beacon/releases/download/v${VERSION}"+curl -fsSLO "${BASE}/${ARCHIVE}"+curl -fsSLO "${BASE}/checksums.txt"++# Verify this exact archive before extracting it, by the name about to be extracted.+grep " ${ARCHIVE}$" checksums.txt | sha256sum --check -++tar -xzf "${ARCHIVE}"mkdir -p ~/.local/bin && mv beacon beacon-hooks beacon-otelcol ~/.local/bin/# ~/.local/bin is already on PATH on most distributions; if `beacon version` fails, add it:@@ -50,6 +60,11 @@ beacon versionbeacon endpoint install```+The version comes from the current release rather than a number you have to keep up to date, and+the architecture comes from `uname -m`: `x86_64` maps to the published `amd64` archive and+`aarch64` to `arm64`. An architecture Beacon does not publish stops the run before anything is+downloaded.+The archive contains three binaries — the `beacon` CLI, the `beacon-hooks` adapter that capturestool activity, and the `beacon-otelcol` collector. All three are needed, and all three arestatically linked with no shared-library dependencies.