Gronk 0.1.6
Pre-releaseUpdate from any earlier build.
New
The preview pane resizes. Drag the divider between the conversation and the
dev-server preview to give either side the room it needs.
Pop the preview into its own window. Handy on a second monitor. Closing that
window puts the preview back in the pane and leaves your dev server running.
The detached window keeps every restriction the docked pane has: sandboxed,
locked to localhost, no bridge to the agent or your files, and its own throwaway
session that writes nothing to disk. Detaching it does not loosen anything.
Changed
Images from the model are never fetched. A remote image in a reply now shows
as a link naming the host it points at, so you decide whether to open it.
Loading one automatically would tell that server you had read the message, and a
unique URL per reply turns an image tag into a tracking pixel that also hands
over your IP.
Images the model generates still appear inline, and images served by your own
dev server in the preview are untouched.
Fixed
- Stopping a popped-out preview flashed "running". Teardown destroyed the
detached window in a way that instantly rebuilt the pane it was removing, so
the dev server was reported alive for a moment after being stopped. - The preview forgot itself after a window reload. The pane read its state
only from live events, so it showed nothing running while the dev server was
still up.
Which file do I want?
| Platform | File |
|---|---|
| Windows | Gronk-0.1.6-windows-x64-setup.exe (installer) or -portable.exe |
| macOS | Gronk-0.1.6-macos-universal.dmg, Apple Silicon and Intel |
| Linux | Gronk-0.1.6-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.
Full detail in CHANGELOG.md.