Agbrte 0.0.5

Which file

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

SHA256SUMS

8873671da010e7ba983c7fc999a90a1140f9b846743d572217940c7056df4508  Agbrte-0.0.5-arm64-mac.zip
f8df70a456698d3a6baa2ccd2bc44a17b699b0000f62fb18ed45f365ec7fe69b  Agbrte-0.0.5-arm64-win.zip
d33ccfa4cf69c0415fb182dc81cd00a6022211bc62c5323e1672355052576e6b  Agbrte-0.0.5-arm64.AppImage
14f5934db9bfa5ef814c8b7d27fd40480fc3ffed23773c582798868c84f656ee  Agbrte-0.0.5-arm64.dmg
397d6163cc056160fb1da99efc5df001a845f6066578db59f7ae1f79ac4133c5  Agbrte-0.0.5-mac.zip
1509f7759ef9b6983db6cc3134196679c09eb50f2ed2bccfea25f19aaa6ccde9  Agbrte-0.0.5-win.zip
2607afe25d5e728517e3db447ff655bbf612b1b84845ec3e133b3043662f245d  Agbrte-0.0.5.AppImage
34c798b91c1b3a55b47e4071ade005ddc1660119d6b94f7f103b542846d3eaa4  Agbrte-0.0.5.dmg
61aec42295d88889c556d661bd4f7b33d247e819bf6759d538971b52760f42aa  Agbrte-Setup-0.0.5.exe
2a46b4ae834f5c037efff44390bc63475158b536925c34b8008eff7ba83e5727  agbrte-0.0.5-arm64.tar.gz
afe3752955a2c77f811d671d428fd4f88e44af0c3dc24725bd0006599ca71655  agbrte-0.0.5.tar.gz
67adb945ea051df1679c9b6e6b7c37998e08c16ebec46253321855b1d49f699f  agbrte_0.0.5_amd64.deb
6e734e4f9ff66e9408014254ce908a6673f80add05ccba29f699f2c2face26dc  agbrte_0.0.5_arm64.deb
3b5c7228d268bdf93091dcca727e51d71052a237e9c63dc2a0fa644558e91163  latest-linux-arm64.yml
519e612d7a0275cb72eeae14ef07e4d68d273d951a483ce7590a5406f4dd4b51  latest-linux.yml
cc727241ebb74ea51801dc6935fd8f10374759a27ec5076f2b9e775cff6c147b  latest-mac.yml
9ff58a63078cb0fb585c4dc05fe0190165444366037bf92cf12d162a3843c1dc  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.