Releases: YounghyeonPark/agbrte
Release list
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.
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.
Agbrte 0.0.11
Which file
| You are on | Download |
|---|---|
| Windows, either architecture | Agbrte-Setup-0.0.11.exe — one installer, both |
| Windows, no installer allowed | Agbrte-0.0.11-win.zip, or -arm64-win.zip |
| macOS, Apple silicon | Agbrte-0.0.11-arm64.dmg |
| macOS, Intel | Agbrte-0.0.11.dmg |
| Linux, anywhere | Agbrte-0.0.11.AppImage, or -arm64 |
| Debian or Ubuntu | agbrte_0.0.11_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 32234799892 from commit 762546fc6c09.
SHA256SUMS
c96ce1836c9f591347f2a16d746568421936e95829d07d10b9fa6dbe2e7a3731 Agbrte-0.0.11-arm64-mac.zip
4e95389d37c03665ea81a43abb2033facd3fb3d1ed6337aad5eff31db0f68a64 Agbrte-0.0.11-arm64-win.zip
4f3e69d21754b8ca121efd99d64591309b28a5274e251e9d0f8132d5dad8b707 Agbrte-0.0.11-arm64.AppImage
b3c18535e6cceb8e44ab79b501dcdf42f5594aa8fd8389e5d3fa544249b83269 Agbrte-0.0.11-arm64.dmg
e230b260c2650fb24bd1bc574170e7181f582583931bf8749b1285fd83115bca Agbrte-0.0.11-mac.zip
30d1f9cd483e09aeab1d6d8dc08c071d14d2b27be6e7f430387216f89c40724f Agbrte-0.0.11-win.zip
d800848a710c1e604c78b9d57ec1e08b2f34d9c258557415d6d03a26ab3d7c72 Agbrte-0.0.11.AppImage
52ccbd2b9cfe8058b25a4bfcc43f3e09ea3e4f90b443d1db7a641a23d3261234 Agbrte-0.0.11.dmg
70044fc9bd3c23d81d6793bc938255a65ba21174201eb7e2c6bf5e78bdb12e95 Agbrte-Setup-0.0.11.exe
e41458939bac2c2bdab5a47d90ba530e1295aef26368a4d5bd8215e953653481 agbrte-0.0.11-arm64.tar.gz
c5639343c9e4a1ebb4844927dbdf3d6de314b5405aa7ef702ac1af0a626f672b agbrte-0.0.11.tar.gz
37ddbb4c63985ffbdd8ea9dc19fcb1db0755577f69165d2a84ad235cf651676f agbrte_0.0.11_amd64.deb
df263a36b133b25ded3c3b79b99966dd6b5072c4c7f97e60104c3454dd29bf15 agbrte_0.0.11_arm64.deb
949a849d733a3a3716ab818f72eeb405ae1ed03325f1a9bc10d65cd0dddbcaa1 latest-linux-arm64.yml
db9077587faab5afe1a71ca1b07f2090116f88264090e05776db0f0e99b03104 latest-linux.yml
5c2fda129d0239b80bfc783cd1dd8c67fb07891f2e4ec655523dc118a327c137 latest-mac.yml
8f393006c218aa95fcca32d57863933cbd305cf401982c8d2eda3d4e5e2bc221 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.
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.
Agbrte 0.0.8
Which file
| You are on | Download |
|---|---|
| Windows, either architecture | Agbrte-Setup-0.0.8.exe — one installer, both |
| Windows, no installer allowed | Agbrte-0.0.8-win.zip, or -arm64-win.zip |
| macOS, Apple silicon | Agbrte-0.0.8-arm64.dmg |
| macOS, Intel | Agbrte-0.0.8.dmg |
| Linux, anywhere | Agbrte-0.0.8.AppImage, or -arm64 |
| Debian or Ubuntu | agbrte_0.0.8_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 32078663844 from commit 6af0fa5c2b7a.
SHA256SUMS
d3104f4c87dd9f3133ec4ac4d56048c2d5ddf396cbfbc61f6610dc52068f5628 Agbrte-0.0.8-arm64-mac.zip
7f11136e1adf31517987e2dc79a956da5cb12b23f70e679a0135639cb22ae0b0 Agbrte-0.0.8-arm64-win.zip
c491f74558b277d4ac45f5d9e6f1efea4dc74412056e2af3a102be7159bd2ba8 Agbrte-0.0.8-arm64.AppImage
f86fc5287dfdd007eee20b728523478fd6473b6660f76f7360f251fa781615ef Agbrte-0.0.8-arm64.dmg
2d2da433e343ff1a448a219a1f481be2ccb4df30fa2fe48c29b2b35aed03b76e Agbrte-0.0.8-mac.zip
51ef1ecd3f0c66d995c46234060b3c972cab8b297bc823c900216b97c79c9994 Agbrte-0.0.8-win.zip
11a6871fab0e9bb394341b6917f5388716cbbfb01d0a33c0e62b3a1e06bb61d6 Agbrte-0.0.8.AppImage
31befb1f338c4495960eed2c81edf75f5dd91cd80564c178cdd31318af984f0e Agbrte-0.0.8.dmg
29b17d166c4ae71b2e6c12bdb7e35e9c3054889e1e6dac0cbe53dd18c928bed9 Agbrte-Setup-0.0.8.exe
4acb0ef926b1f2a252751241e1921869acfc75f15c21d756034ea43848e4f1b7 agbrte-0.0.8-arm64.tar.gz
eb28fba4abaf2c91179fd3902264305da4cc37f5d1091122d53a0c9e6c5a871d agbrte-0.0.8.tar.gz
9ee94458682843351de3b0787fb8e332525e6f06533810119206c8b61ab59286 agbrte_0.0.8_amd64.deb
4babeee3441bd3629d368da3f0f2b889e5ca69876143b79501c29d5ed57b1586 agbrte_0.0.8_arm64.deb
769061d80acf9898edb7b7fe19618e8a0db8caefe933a9250ea5e91cbdd55875 latest-linux-arm64.yml
6a92be0a5fe4ba3cb02da097f9c5181aa5cd617b6435c1d46b38876595bb1f1c latest-linux.yml
6ecf318b8dc338e65009cb3424285447b064ac56fc32cd31642c1c1d5896708e latest-mac.yml
7792af85b88bacdc26bf5c8bb102ed6162caf0fa77d8a599ba552b6bc45217fa 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.
Agbrte 0.0.7
Which file
| You are on | Download |
|---|---|
| Windows, either architecture | Agbrte-Setup-0.0.7.exe — one installer, both |
| Windows, no installer allowed | Agbrte-0.0.7-win.zip, or -arm64-win.zip |
| macOS, Apple silicon | Agbrte-0.0.7-arm64.dmg |
| macOS, Intel | Agbrte-0.0.7.dmg |
| Linux, anywhere | Agbrte-0.0.7.AppImage, or -arm64 |
| Debian or Ubuntu | agbrte_0.0.7_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 32028338433 from commit a02d22daffee.
SHA256SUMS
f5716075c0b5ecf8d74c412afe0261909eca01cbe8b9d9384174524f96f4039e Agbrte-0.0.7-arm64-mac.zip
77f69eed341b4133c13da5bd1848e229837d8d29bfc74f2d175da790217d5998 Agbrte-0.0.7-arm64-win.zip
1a2a304b4c186b5f29ab960c85ce6136c6ae18cf778c56a3436d93570329a815 Agbrte-0.0.7-arm64.AppImage
c1ad662a910bd4223af13b01f149ce4e242eae98bb08b40254b794e4de5e64a8 Agbrte-0.0.7-arm64.dmg
babb76b4172d31e0585688c781ddbb9d2c53fe94bead94d291f7bfc57ff8eaf3 Agbrte-0.0.7-mac.zip
6c544023b10ebed7c95d5217dd5625b2b1efda9012d5bb577c31b38e86342bc4 Agbrte-0.0.7-win.zip
8400674f04cdf408a98251122cee97cd96e79ddbc4cbd9303f046d2283003d2e Agbrte-0.0.7.AppImage
1f2c7ea18e5d9d7153bfc885181b3c2fc322f5cb1934315360f54c802a254ef6 Agbrte-0.0.7.dmg
ff776946aa9a337986c8784faefdbd87824c6b6941f6130132d8661b674e7ca4 Agbrte-Setup-0.0.7.exe
ed35064d82126e42017878895cd16aee1ad82c3afffadbb872053f86aa15b9ae agbrte-0.0.7-arm64.tar.gz
771d1eba3bba885e1172c4540f864e5b4335ce17ef40d1fdc0c65bf6f6eb6d09 agbrte-0.0.7.tar.gz
f0a63127e4f61ccd97a62f6d54d6b9e265ec80dcf8b5ffdc8a6cf5e8fa0f53d6 agbrte_0.0.7_amd64.deb
467a7a68b1a3e35301f655b75eeaae8a80ad70daa2d42461fecbe8d5a87d085f agbrte_0.0.7_arm64.deb
33e422818ccae7d6010a6e390c27ceb5792dc4087293c04c5628e31f92029b16 latest-linux-arm64.yml
dacc460864705959797edc83298f04d87198d9d11224744a6e3bece4a4fad2da latest-linux.yml
239d785cfd05d7b5eebd8500fc3f8fa24405e59ba8ba05d4f69e8a8360da4100 latest-mac.yml
e10a18f53aee7b702c3e8512291ada3d90f07e468c8407c58b42091b892c3c00 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.
Agbrte 0.0.6
Which file
| You are on | Download |
|---|---|
| Windows, either architecture | Agbrte-Setup-0.0.6.exe — one installer, both |
| Windows, no installer allowed | Agbrte-0.0.6-win.zip, or -arm64-win.zip |
| macOS, Apple silicon | Agbrte-0.0.6-arm64.dmg |
| macOS, Intel | Agbrte-0.0.6.dmg |
| Linux, anywhere | Agbrte-0.0.6.AppImage, or -arm64 |
| Debian or Ubuntu | agbrte_0.0.6_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 31942258164 from commit 440f072ebe6f.
SHA256SUMS
cbfc220e7d420d0a2f860a814d3f1caef968e522216915efdbc1d5392add6a9e Agbrte-0.0.6-arm64-mac.zip
355fc6c3a235aa60cfff618e3a87a064b628aeff777c559b4bbf7f5d63482472 Agbrte-0.0.6-arm64-win.zip
283a66b426242d5f61a7f4bb087088434da32eea5071261fed88185af49ce195 Agbrte-0.0.6-arm64.AppImage
ec12adc36f39d2d8104e0409333901cd37bf7ad6d4ddcc8f6974643b5f9b9bd1 Agbrte-0.0.6-arm64.dmg
5a355626dd5fd78ad65571182c94cb51994eb1a842dc2d4fe612e7e8c4eec2bd Agbrte-0.0.6-mac.zip
1ab3c7b814082c14a4716148ee7f2539dc669f65d5d2e169433fa5235aebeca8 Agbrte-0.0.6-win.zip
c40c703977b9f31c1d1e3baaed3e1fd05d453b60b8b45cb66db9ba13bc858efe Agbrte-0.0.6.AppImage
ec64da7e74269248b61454c8c83a07b8e24d7841dd692ef687fc5f8718f06d8e Agbrte-0.0.6.dmg
cc690ffda799322e1a19acc4b6df976fd1c5aebd84fb69b5606a6e9afc3d29ce Agbrte-Setup-0.0.6.exe
f54efa260686a444cb6d93c5616212b95ecae23027821475af07646d49d50954 agbrte-0.0.6-arm64.tar.gz
af8e6ca4cf25a2a7b1b39c7196f349551935491f38b5e3acf905a982bd00abb7 agbrte-0.0.6.tar.gz
8affdf9a9a5ffad95796f13172b00f37f23bae9b144d34f428fdad67d6a44497 agbrte_0.0.6_amd64.deb
950dc04719f9575d3bb09fa3d134dd8d30592abfeef507e605233c02c171ae5f agbrte_0.0.6_arm64.deb
541f402eac5ee595054155deefc9144e351c197f5b83b2dbaa30e269302d9ea8 latest-linux-arm64.yml
9f86c5a44f5524250c699c7b7f6e83c156b0fd2c6acae3b05f75abd13cc602fb latest-linux.yml
1a0516bd524ed8b26ae147e5e8ec9f82c5db8586b5377e9b0f740f97286ad5ed latest-mac.yml
89f301dc8fe89b4a401c42c76e43384e68b327f501acb3eb23eb98ab61f9ce2e 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.
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.
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.