Gronk 0.1.7
Pre-releaseUpdate from any earlier build. A small fix release over 0.1.6.
Fixed
An image could be refused from a folder that was allowed. When the agent
referred to an image, Gronk checked it against a list of permitted folders. One
side of that comparison followed shortcuts on disk and the other did not, so a
folder reached through one never matched, and a file genuinely inside a
permitted folder was rejected with "Path outside allowed image roots".
macOS was most affected, because its temporary folder is reached that way by
default. The containment check itself is unchanged in strictness: both sides are
now resolved the same way, which is the comparison it was always meant to make.
Everything in 0.1.6 is still here: the resizable preview split, the pop-out
preview window, and remote images from the model shown as links rather than
fetched.
Which file do I want?
| Platform | File |
|---|---|
| Windows | Gronk-0.1.7-windows-x64-setup.exe (installer) or -portable.exe |
| macOS | Gronk-0.1.7-macos-universal.dmg, Apple Silicon and Intel |
| Linux | Gronk-0.1.7-linux-x86_64.AppImage or -amd64.deb |
Node.js is not required. You do need the Grok CLI and your own
Grok account.
These installers are unsigned
macOS will say the app is damaged. It is not. Right-click and choose Open,
then confirm. Double-clicking will not work until you have done that once.
Windows SmartScreen: More info, then Run anyway.
SHA256SUMS.txt verifies the download arrived intact. That checks integrity, not
authorship. Only signing does that.
Known limitations
- Developed and tested on Windows. The macOS and Linux builds come from CI and
have not been run by the author. - No automatic updates.
- Conversations are stored on your machine as readable text. Do not paste secrets
into a chat. - Grok cannot yet ask you a question mid-task. When it tries, you will see
"Agent requested unsupported client method" and it will pick a default and
carry on.
Full detail in CHANGELOG.md.