Agbrte 0.0.8
Which file
| You are on | Download |
|---|---|
| Windows, either architecture | Agbrte-Setup-0.0.8.exe — one installer, both |
| Windows, no installer allowed | Agbrte-0.0.8-win.zip, or -arm64-win.zip |
| macOS, Apple silicon | Agbrte-0.0.8-arm64.dmg |
| macOS, Intel | Agbrte-0.0.8.dmg |
| Linux, anywhere | Agbrte-0.0.8.AppImage, or -arm64 |
| Debian or Ubuntu | agbrte_0.0.8_amd64.deb, or _arm64 |
These builds are not signed
macOS will report an unidentified developer and Windows SmartScreen will
warn. That is what an unsigned build is, and saying so is more useful
than a workaround: signing needs an Apple Developer account and a
Windows code-signing certificate, and neither exists for this project
yet.
What you can verify
Every file carries signed build provenance. It says which repository,
workflow, commit and run produced it, signed through Sigstore:
gh attestation verify <file> --repo YounghyeonPark/agbrte
That is not the same as code signing, and it does not stop the warnings
above — nothing in the operating system looks at it. What it answers is
the question a checksum cannot: not "do these bytes match a list", but
"who built this, from what source". A list of digests can be replaced by
whoever can replace the file beside it; this cannot.
SHA256SUMS is attached as well, and printed below, for comparing by
hand when gh and a network are not to hand.
Built by run 32078663844 from commit 6af0fa5c2b7a.
SHA256SUMS
d3104f4c87dd9f3133ec4ac4d56048c2d5ddf396cbfbc61f6610dc52068f5628 Agbrte-0.0.8-arm64-mac.zip
7f11136e1adf31517987e2dc79a956da5cb12b23f70e679a0135639cb22ae0b0 Agbrte-0.0.8-arm64-win.zip
c491f74558b277d4ac45f5d9e6f1efea4dc74412056e2af3a102be7159bd2ba8 Agbrte-0.0.8-arm64.AppImage
f86fc5287dfdd007eee20b728523478fd6473b6660f76f7360f251fa781615ef Agbrte-0.0.8-arm64.dmg
2d2da433e343ff1a448a219a1f481be2ccb4df30fa2fe48c29b2b35aed03b76e Agbrte-0.0.8-mac.zip
51ef1ecd3f0c66d995c46234060b3c972cab8b297bc823c900216b97c79c9994 Agbrte-0.0.8-win.zip
11a6871fab0e9bb394341b6917f5388716cbbfb01d0a33c0e62b3a1e06bb61d6 Agbrte-0.0.8.AppImage
31befb1f338c4495960eed2c81edf75f5dd91cd80564c178cdd31318af984f0e Agbrte-0.0.8.dmg
29b17d166c4ae71b2e6c12bdb7e35e9c3054889e1e6dac0cbe53dd18c928bed9 Agbrte-Setup-0.0.8.exe
4acb0ef926b1f2a252751241e1921869acfc75f15c21d756034ea43848e4f1b7 agbrte-0.0.8-arm64.tar.gz
eb28fba4abaf2c91179fd3902264305da4cc37f5d1091122d53a0c9e6c5a871d agbrte-0.0.8.tar.gz
9ee94458682843351de3b0787fb8e332525e6f06533810119206c8b61ab59286 agbrte_0.0.8_amd64.deb
4babeee3441bd3629d368da3f0f2b889e5ca69876143b79501c29d5ed57b1586 agbrte_0.0.8_arm64.deb
769061d80acf9898edb7b7fe19618e8a0db8caefe933a9250ea5e91cbdd55875 latest-linux-arm64.yml
6a92be0a5fe4ba3cb02da097f9c5181aa5cd617b6435c1d46b38876595bb1f1c latest-linux.yml
6ecf318b8dc338e65009cb3424285447b064ac56fc32cd31642c1c1d5896708e latest-mac.yml
7792af85b88bacdc26bf5c8bb102ed6162caf0fa77d8a599ba552b6bc45217fa latest.yml
What this is
A desktop app and a CLI for running coding agents. Sessions belong to a
host process per workspace rather than to the window, so closing the app
is not a reason to stop work, and a session on another machine needs
nothing installed there beyond what Agbrte unpacks into ~/.agbrte.