Agbrte 0.0.4
Which file
| You are on | Download |
|---|---|
| Windows, either architecture | Agbrte-Setup-0.0.4.exe — one installer, both |
| Windows, no installer allowed | Agbrte-0.0.4-win.zip, or -arm64-win.zip |
| macOS, Apple silicon | Agbrte-0.0.4-arm64.dmg |
| macOS, Intel | Agbrte-0.0.4.dmg |
| Linux, anywhere | Agbrte-0.0.4.AppImage, or -arm64 |
| Debian or Ubuntu | agbrte_0.0.4_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 31616875451 from commit b52e6bbd1c93.
SHA256SUMS
704fa36cfd0a482d40a3eda49234912a61c3fd4d0bc326b6fd889d42912fc39e Agbrte-0.0.4-arm64-mac.zip
b7b49ce7795762d0f18ef77eefe9689ee82190fbb087253ac0de0a8e7904787f Agbrte-0.0.4-arm64-win.zip
05c131ed45266bbf4224bfe9d0f33b43112345db9564774ec81c4419d722d3b4 Agbrte-0.0.4-arm64.AppImage
0a1c1a5c81174bff4ab81a6775cf996153ca80266774a5124730fcf074a28e5f Agbrte-0.0.4-arm64.dmg
b8fde56d297ecc86fba2c00ff5cf3fcf6e4b2b5e9c8e171fcc2ac0751de4a3c7 Agbrte-0.0.4-mac.zip
a2b3f864744fbacc01833a6a0e37502ccabbea26d2a32059dfb774a447fa3875 Agbrte-0.0.4-win.zip
d693fb734087136ea3335f7a2920db296491357a3cc7cc9876148cafb5148ee3 Agbrte-0.0.4.AppImage
04df2413884d8c97a519b590b7c93fbf21e33f8fc64dcb8db19b7048b9cd7d8c Agbrte-0.0.4.dmg
0f1a6e150d72b8b46a9f7d1e91c04c863269cac8465147a22a2692719359c025 Agbrte-Setup-0.0.4.exe
30568a1c74ff6ad7f58c5a5bce7085ddeb51aab6643d60639db46b58242ada1a agbrte-0.0.4-arm64.tar.gz
72b9af25c5d45f711240b822d7268135a8059ebbf900a69163906c4c7def62c6 agbrte-0.0.4.tar.gz
22c669255aee01cd998333d987ee9a0691e6f4661cd1ba952610bc292d8a743c agbrte_0.0.4_amd64.deb
0250eb5336c166ec878a7f9cee3f40d9d717f30ad98c9764f636f6f918d3be3a agbrte_0.0.4_arm64.deb
4803ee6e3540f08a94bd163652ec05b81168ffe43108d7878a9971e2f650d3b3 latest-linux-arm64.yml
7911c8d381959d513b2655469a22d837ed18f772e049a8108dd286116dea982f latest-linux.yml
25972e8300ddd85dccf3a13236f7d0922afc1c691d3b1d1e6c61e07b7958ba22 latest-mac.yml
3230e0fddfabe2ac5c105197a484cc1e1c9fe63c6d385c0b0ff0691b032a9113 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.