Agbrte 0.0.9

Which file

You are on	Download
Windows, either architecture	Agbrte-Setup-0.0.9.exe — one installer, both
Windows, no installer allowed	Agbrte-0.0.9-win.zip, or -arm64-win.zip
macOS, Apple silicon	Agbrte-0.0.9-arm64.dmg
macOS, Intel	Agbrte-0.0.9.dmg
Linux, anywhere	Agbrte-0.0.9.AppImage, or -arm64
Debian or Ubuntu	agbrte_0.0.9_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 32123289654 from commit 0e766992dfc6.

SHA256SUMS

19f04ee2ca87b3c49c85955790881486a77585e8e43c7b1e3262fc13807560a7  Agbrte-0.0.9-arm64-mac.zip
c695db2efa604a605fe2a7819e5e5d0ca6265015d2d017037177229c237233b3  Agbrte-0.0.9-arm64-win.zip
5d132f676a36facf435a214fe1eeb59a0090adc51001c55fe0d73d052159b9b7  Agbrte-0.0.9-arm64.AppImage
9ac8c131ba30d502cdbdb08349cd42fc16b473616284afd172096c3fc9f8d16d  Agbrte-0.0.9-arm64.dmg
3cdcdc6d653efedbb9eed20c0d8e6535ea3486a5d660add696c63bd06047c406  Agbrte-0.0.9-mac.zip
0f3d52e34e631aa399d8e21f7b07e47a229955c97d738472e2e0c32c1e8f41e9  Agbrte-0.0.9-win.zip
5d7791434869e1d04c9a2cd732e59079903877113b27ef95952a9037419a3a88  Agbrte-0.0.9.AppImage
0503e9a2652bd29764629cdd352da083bd3f279bf6e18729d18ad18cd864baea  Agbrte-0.0.9.dmg
68c7e213a2a3f18887e62b5a2de6bc354d364e8cf9cedca95d17330283807478  Agbrte-Setup-0.0.9.exe
081cedbef2d3ac6cfbb7f01db9245cdfa4af2cce56f773130513521c90df2eac  agbrte-0.0.9-arm64.tar.gz
b851f92006cf9d4f4100511fdd1522d39517bd4ad3e01116907758dbd2d440b3  agbrte-0.0.9.tar.gz
cd1a3f99493da31c3873262660a2ba33ebcba964f29bde684bbf2517870d072a  agbrte_0.0.9_amd64.deb
4a47433f9db769cc5b74a5c9674fdbc570eeb236a24f3ce7d51977a5d0f84f55  agbrte_0.0.9_arm64.deb
ccac9b96b53177985159318fd8b74b7d91cbb08a45611b0ed0789e56ff725e6a  latest-linux-arm64.yml
7eebd4880d4778349e2c0fb7a4aa60d45e3c42e1bab012bd274fdda4f2a3cabb  latest-linux.yml
cb58e957bc01b198d81abf35a8b64938c9ba35a2ea5e441fdd36cd02d608669a  latest-mac.yml
cd5ea4b00fbe4abe9034b3424ddeb82b69ff019d60386d502db1b96ae917375a  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.