Agbrte 0.0.26
What changed
- Put a token in front of the browser client, because the address was never a lock
- End the options before the prompt, or a variadic flag eats it
- Let an installed CLI use the login it already has
- Ask again when a model is billed for saying nothing, and say so when it persists
- Let two sessions in a group actually reach each other
- Photograph the product rather than the fixture
- A README that introduces, and documents that explain
Each line is one commit, and its message says what the defect was and why the fix is shaped the way it is: v0.0.25…v0.0.26
Which file
| You are on | Download |
|---|---|
| Windows, either architecture | Agbrte-Setup-0.0.26.exe — one installer, both |
| Windows, no installer allowed | Agbrte-0.0.26-win.zip, or -arm64-win.zip |
| macOS, Apple silicon | Agbrte-0.0.26-arm64.dmg |
| macOS, Intel | Agbrte-0.0.26.dmg |
| Linux, anywhere | Agbrte-0.0.26.AppImage, or -arm64 |
| Debian or Ubuntu | agbrte_0.0.26_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 32997178711 from commit 263ce81ecf38.
SHA256SUMS
51ce99f5b81af96355674f8799ef8f96f9ed9db87d652ea9dcffe306a57af596 Agbrte-0.0.26-arm64-mac.zip
db422fe2cac9ea26525f35e6dc3002605d1c75478b801be45d70222e6d65d403 Agbrte-0.0.26-arm64-win.zip
12bf1d3cfb0c081ef9f2f764c137390e6835e67040a667c7ee767f59c775d58b Agbrte-0.0.26-arm64.AppImage
24e3f0d5b33d2d9955652a3418474c60ac2c242591f786896b45beaceebc6db2 Agbrte-0.0.26-arm64.dmg
b40f3ce95aa1edfc06346a388d6a4291901faa03f0b7ca37f8efca61e2a5ee6e Agbrte-0.0.26-mac.zip
5122eeb2690d94658f0d0ad100b7c104285ef04214edbf3fdc116ff8d9a54f2d Agbrte-0.0.26-win.zip
9edb6e3fcf7f719f758138d49fed21b8c86685ccd446237936619b9212812cd5 Agbrte-0.0.26.AppImage
fb2b82b58749823c1b29442a444134b41fcbd450fb45d0f5438093b859cf673d Agbrte-0.0.26.dmg
3b164b2366cf200be3b2183e04613e6a74e3c31222b3d2d36dde49153916deeb Agbrte-Setup-0.0.26.exe
e40568618d97c3edbe2f526b3dee8ddbd79a419d812973c440ca0821fa9360fc agbrte-0.0.26-arm64.tar.gz
c75ee88c5bb157270ec4e3d44fbc31fcd42bc56bdb8fe0fc3ace3f86309aa677 agbrte-0.0.26.tar.gz
c94b1e1ca79e44a47b7b9c342d274de628e7cfad4152a0e11484935521438dba agbrte_0.0.26_amd64.deb
93b799fafd3d1eca9e0c53af97e769a555d1e9347b57e17d0011136eb54e09b0 agbrte_0.0.26_arm64.deb
9b748672c517580f46ba8ab89eee0b6fcbb25ca64832d21741bda18fb98a8dea latest-linux-arm64.yml
728c1625c22cc6852606920d849a088306246d63f24891081d6c640617d57f03 latest-linux.yml
6e8ceb688ce5e6b067429aa66051e73dca1cfe5a0e6be7126b8728d81f4757ec latest-mac.yml
63d1fa4b534d509adf426c037d31713af123fffd98556900fccc47d0b63aa19c 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.