The signed, self-service install channel for the Burrowee platform.
Each installer detects your OS and architecture, verifies the download
end-to-end (minisign signature → SHA-256 → unzip), then drops the burrowee
dispatcher plus the component. burrowee <comp> … and the bare
burrowee-<comp> binary both work.
curl -fsSL --proto '=https' --tlsv1.2 https://release.burrowee.com/cli/install.sh | sh
curl -fsSL --proto '=https' --tlsv1.2 https://release.burrowee.com/gateway/install.sh | sh
curl -fsSL --proto '=https' --tlsv1.2 https://release.burrowee.com/edge/install.sh | sudo sh
curl -fsSL --proto '=https' --tlsv1.2 https://release.burrowee.com/agent/install.sh | sh
Every release ships SHA256SUMS.txt and a minisign signature.
The signing public key lives at
/burrowee-release.pub — it is also baked into the
installer, which is the trust anchor that verifies each download automatically. To check
a download yourself:
minisign -V -P "$(cat burrowee-release.pub | tail -n1)" -m SHA256SUMS.txt -x SHA256SUMS.txt.minisig
f=<file> # the file you downloaded
want=$(awk -v f="$f" '{ n = $2; sub(/^\*/, "", n); if (n == f) { print $1; exit } }' SHA256SUMS.txt)
got=$(shasum -a 256 "$f" | awk '{print $1}') # sha256sum "$f" on Linux
if [ -z "$want" ]; then echo "NO ENTRY for $f in SHA256SUMS.txt — do not install"
elif [ "$want" = "$got" ]; then echo "OK $f"
else echo "MISMATCH for $f — do not install"; fi
A failed signature check means the bytes are untrusted — do not install them.
| OS | arm64 | amd64 |
|---|---|---|
| macOS (darwin) | ✓ | ✓ |
| Linux | ✓ | ✓ |
Windows is not supported.
Full user guides — getting started, install, gateway, CLI, and reference:
Skill packages for fresh-context LLM agents — point an agent at any of these: