Agbrte 0.0.11
Which file
| You are on | Download |
|---|---|
| Windows, either architecture | Agbrte-Setup-0.0.11.exe — one installer, both |
| Windows, no installer allowed | Agbrte-0.0.11-win.zip, or -arm64-win.zip |
| macOS, Apple silicon | Agbrte-0.0.11-arm64.dmg |
| macOS, Intel | Agbrte-0.0.11.dmg |
| Linux, anywhere | Agbrte-0.0.11.AppImage, or -arm64 |
| Debian or Ubuntu | agbrte_0.0.11_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 32234799892 from commit 762546fc6c09.
SHA256SUMS
c96ce1836c9f591347f2a16d746568421936e95829d07d10b9fa6dbe2e7a3731 Agbrte-0.0.11-arm64-mac.zip
4e95389d37c03665ea81a43abb2033facd3fb3d1ed6337aad5eff31db0f68a64 Agbrte-0.0.11-arm64-win.zip
4f3e69d21754b8ca121efd99d64591309b28a5274e251e9d0f8132d5dad8b707 Agbrte-0.0.11-arm64.AppImage
b3c18535e6cceb8e44ab79b501dcdf42f5594aa8fd8389e5d3fa544249b83269 Agbrte-0.0.11-arm64.dmg
e230b260c2650fb24bd1bc574170e7181f582583931bf8749b1285fd83115bca Agbrte-0.0.11-mac.zip
30d1f9cd483e09aeab1d6d8dc08c071d14d2b27be6e7f430387216f89c40724f Agbrte-0.0.11-win.zip
d800848a710c1e604c78b9d57ec1e08b2f34d9c258557415d6d03a26ab3d7c72 Agbrte-0.0.11.AppImage
52ccbd2b9cfe8058b25a4bfcc43f3e09ea3e4f90b443d1db7a641a23d3261234 Agbrte-0.0.11.dmg
70044fc9bd3c23d81d6793bc938255a65ba21174201eb7e2c6bf5e78bdb12e95 Agbrte-Setup-0.0.11.exe
e41458939bac2c2bdab5a47d90ba530e1295aef26368a4d5bd8215e953653481 agbrte-0.0.11-arm64.tar.gz
c5639343c9e4a1ebb4844927dbdf3d6de314b5405aa7ef702ac1af0a626f672b agbrte-0.0.11.tar.gz
37ddbb4c63985ffbdd8ea9dc19fcb1db0755577f69165d2a84ad235cf651676f agbrte_0.0.11_amd64.deb
df263a36b133b25ded3c3b79b99966dd6b5072c4c7f97e60104c3454dd29bf15 agbrte_0.0.11_arm64.deb
949a849d733a3a3716ab818f72eeb405ae1ed03325f1a9bc10d65cd0dddbcaa1 latest-linux-arm64.yml
db9077587faab5afe1a71ca1b07f2090116f88264090e05776db0f0e99b03104 latest-linux.yml
5c2fda129d0239b80bfc783cd1dd8c67fb07891f2e4ec655523dc118a327c137 latest-mac.yml
8f393006c218aa95fcca32d57863933cbd305cf401982c8d2eda3d4e5e2bc221 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.