Agbrte 0.0.25
Which file
| You are on | Download |
|---|---|
| Windows, either architecture | Agbrte-Setup-0.0.25.exe — one installer, both |
| Windows, no installer allowed | Agbrte-0.0.25-win.zip, or -arm64-win.zip |
| macOS, Apple silicon | Agbrte-0.0.25-arm64.dmg |
| macOS, Intel | Agbrte-0.0.25.dmg |
| Linux, anywhere | Agbrte-0.0.25.AppImage, or -arm64 |
| Debian or Ubuntu | agbrte_0.0.25_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 32816274409 from commit 7edca4c887d3.
SHA256SUMS
c01b6e74611b43534ff14e4f36d97b2ff807c9b8368dc3a4c429c25cc9e87fb4 Agbrte-0.0.25-arm64-mac.zip
e27897f6e1e1c6df07ac620101f7fece39d1ef62dc8cda349c3e5f0d569b6184 Agbrte-0.0.25-arm64-win.zip
4f9b715c35b1caa3b5a3b3bda6af9ed89b504d7812bdedbfb2ead65eb52fea90 Agbrte-0.0.25-arm64.AppImage
8e6f6d65f974a742d18856463063f8918854bbb90bce8f13463d256a9134cf13 Agbrte-0.0.25-arm64.dmg
6af3c2822755ac2531187b1ad741465b680a4861dd6a8cd63758ab278fe4ab80 Agbrte-0.0.25-mac.zip
16582b138d4b095bf2afdc960d55c6e94f02be609dce5d7b6a186dd08f883bae Agbrte-0.0.25-win.zip
eea4f7b4afc66b00b2465e33887640e59914184558d9e68e76e18648c52d31f3 Agbrte-0.0.25.AppImage
631cd27d88c3340cd76c2de312b5dcc51813289aca05dd2975b1d16803d29e6c Agbrte-0.0.25.dmg
4e6585e420253c96e7fc3009415e1062f890522455adb85048386e0ecd696c82 Agbrte-Setup-0.0.25.exe
86c43fb8cdca0306cb571538e4fa3a142453fd9130e986e81cba41a9a46f5c3f agbrte-0.0.25-arm64.tar.gz
b81cfbb8ccbac10b3f73f3619c2e224161ba13e9ec8248ae027ef7512be52583 agbrte-0.0.25.tar.gz
6f2d8916e41dca12d1cd39ab99259c3437086e4ee29bab4b2c95d903af8c98aa agbrte_0.0.25_amd64.deb
0fa197419b737f863b400a95ac8c2330f03d574d47fb4010bd1ada1d32dcc640 agbrte_0.0.25_arm64.deb
b451f001e6396b0be0d1c59a689236cd6771de37a2d742a7da7ebb6340af4a0c latest-linux-arm64.yml
82d793a4aec148afa54e2116381e86404eab3ed605534985ea42218c63d822e8 latest-linux.yml
5846d2cb36f42c5b2822fe89bcca99f3b002cef44a257093840612685ef8aa72 latest-mac.yml
30ecb0e6aa2d821e14a1128f29edd791e28348d0652b6ec64beee64f727a0cdf 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.