Gronk 0.5.1

Follow-ups to 0.5.0, and one message that was actively misleading.

Added

• Slash-command completion. Typing / offers the commands the running session accepts, filtered as you type, with arrows and Enter or Tab to complete. The list comes from the agent itself, so it only ever shows commands that work here.
• AGENTS.md, so any agent picking up the repo starts with the project's rules.

Changed

• Menu buttons are vertical dots. A long title that gets cut off ends in three dots of its own, which sat right beside the old horizontal menu dots and read as two buttons.
• One menu implementation across the app. The browse lists now use the same control as everywhere else: keyboard-reachable for the first time, and dismissing it no longer activates whatever was underneath.

Fixed

• Running out of Grok Build usage now says so. It arrives under the same error code as a genuine crash, so the app called it a fault and suggested retrying — which never works, because a spent balance does not clear by retrying.
• Deleting a session from a browse list asks first, in place, instead of a dialog that froze the rest of the app.

Checksums

4c48ed188e949c0c304f39ef4fd1b970bad2db007d6f69e95361e2b47ed193e5  Gronk-0.5.1-universal-mac.zip
13543979096e41bfe4326b805da4aab0e4c1f704656233788a1960c40c377887  Gronk-0.5.1-universal.dmg
bf0e789b83597a8dfe7dead1680beead74893e572884aaad66404171bad5ec68  Gronk-0.5.1.AppImage
edb4ea16e303d394c7ad74da4d3f04e126320ffc70cdfeabf61d1d66b852a9fa  Gronk.0.5.1.exe
1b5aacfb82cb7021bfb2c698276e621cad52912ac746793ab01257172bc4ebe1  Gronk.Setup.0.5.1.exe
daeb0b75c67df18c0ba6e5470c1b61671e9439a564c1df9ae9e2eb12729c2a87  gronk_0.5.1_amd64.deb

Installers are unsigned: Windows will warn, macOS needs right-click → Open.

Gronk 0.5.0

Model handling, end to end — switching one no longer costs you the conversation, the app can follow grok's default instead of pinning a model forever, and grok 4.6's reasoning effort is exposed. Plus the app now tells you what changed after an update, and stops explaining itself once you have used it.

Added

• Reasoning effort, from grok 4.6. Settings offers the levels the chosen model actually reports — four on 4.6 including Extra High, three on 4.5. Leaving it unset lets the model use its own default. Applies to new sessions.
• A "Follow grok" option for the model. New sessions use whatever grok defaults to, so a newer model arrives without anyone doing anything. Settings states which of the two you are on.
• The model list stays current while the app runs. The agent announces when a model is added or removed from the account, and every menu follows without a restart. Verified against the Grok CLI's 1.0 line.
• The context window of the model in use, in the usage panel, as the agent reports it.
• A What's New note after an update, shown once per version. A fresh install sees nothing.

Changed

• Switching model keeps the conversation. It used to restart the agent, and a restart is a new session with an empty transcript.
• The model menu and Settings answer different questions. The menu changes the conversation in front of you and stores nothing; Settings is what new sessions start with.
• The app retires its own introduction once a turn has been completed.

Fixed

• A usage limit reads as a usage limit, not as a crash — including the part of the reply that says how much you have used and when it resets, which was being dropped before it reached the screen.
• Choosing the model already in use does nothing, instead of replacing the conversation with an empty session.
• Security and stability improvements.

Checksums

2db8e724a1839420b3042bf8933cc8fa46d6b51369055ba3b0315e7536180d14  Gronk-0.5.0-universal-mac.zip
05469210cb99ea686f400fac5a79d91b1e3a33f209bde82b23c00cba28266893  Gronk-0.5.0-universal.dmg
bbfcb9053a4d6b01ed3501230fecb7afd109563b3f2e08d41ecd08286f5fee45  Gronk-0.5.0.AppImage
cdf1f034399230ec62cd8672a5846f1209f1751eb6fadfe59d596caeb6750218  Gronk.0.5.0.exe
9cffd904cd2290c49e165bace85e9d638eedb2d397af39973265214d64275330  Gronk.Setup.0.5.0.exe
3be7ba8223b5f29b20f501be772989f8e7be6aca06b2ecd5ad388af0ae4060c8  gronk_0.5.0_amd64.deb

Installers are unsigned: Windows will warn, macOS needs right-click → Open.

Gronk 0.4.1

A correction and a fix. If you are on 0.4.0, take this one — 0.4.0 gives wrong advice
when a turn fails.

Fixed

A failed turn no longer suggests the wrong cause. 0.4.0 said that a bare "Internal
error" from the agent probably meant a spent plan quota, and told you to check your usage
limits. That is wrong. The Grok CLI reports rate limits on their own error code with their
own message about upgrading, and treats "Internal error" as a server fault specifically
not a rate limit — so a real quota block arrives clearly labelled, and the advice pointed
at the one thing the CLI would already have told you about. The message now says what the
code actually means: a well-formed request that failed inside the agent, worth retrying. It
guesses at nothing.

History from one conversation can no longer be painted into another. Opening a session
can return a different session than the one you clicked, so the app had to accept restored
history for a conversation it had not heard of yet. That left a window, while a session was
opening, where an unrelated session finishing its own startup could repaint what you were
reading — and the save that follows would store it under the name of the conversation you
thought you were in. Each open is now named, and restored history is only accepted from the
open it answers.

Upgrading

Straight over 0.4.0, nothing to migrate. The 0.4.0 note about not going back to 0.3.0 or
earlier still applies: conversations live in one file each now, and older versions read them
out of the store, so they would show every session as empty.

---

Verify a download against SHA256SUMS.txt before running it.

Gronk 0.4.0

Two things happened in this release. Sessions stopped being one-at-a-time, and the
transcript stopped living in one file that got slower the bigger it grew. Most of the rest
follows from those.

Before you install this

Do not go back to 0.3.0 or earlier after running this. Conversations move out of
gronk-store.json into one file each, and the store is rewritten without them. Older
versions read the conversation out of the store, so they would show every session as empty.
Nothing is destroyed — the files are still there and this version reads them — but anything
said while downgraded is written where this version no longer looks.

Added

Sessions keep running when you look at another one. Clicking a different session used to
end the work you walked away from. Several can now run at once, the sidebar marks which are
working and which are waiting on you, and each row can be stopped on its own. Coming back to
one shows what it actually says rather than what was half-drawn when you left.

A message typed while the agent is working is queued instead of refused. Send used to be
disabled for the whole turn, so a finished message sat in the box waiting for an end you
cannot see coming. Queued messages are shown in full, each cancellable, and they go in order
as turns finish. Stopping a turn holds them rather than releasing the next one — stopping
usually means you want to say something different — and the button says so.

What you have typed stays with the conversation you typed it in. Leaving the conversation
view used to throw an unsent message away, and switching sessions carried it into the next
conversation, one Enter from the wrong agent. Drafts are kept per conversation, including one
typed before the agent has finished starting. They do not survive quitting the app.

A Changes panel showing what the agent altered in the open folder, and project notes —
plain text, one per folder, kept with Gronk's own settings rather than in the project.

Changed

The transcript store no longer grows without bound. Conversations live in one file each,
so opening a session reads that session rather than everything ever said. A real store had
reached 120 MB, most of it duplicated tool calls re-appended on every reopen, and parsing it
froze the window for about a minute on every read. The duplicates are removed on first launch
and cannot re-accumulate.

The store is read once per operation rather than eighteen times. A single turn was
re-reading and rewriting the whole file repeatedly; the permission audit now has its own file.

Chat and Build have the same shape, and the sidebar says what each one is for. Archived
sessions sit with the sessions rather than in the app footer.

Fixed

A transcript save cannot replace a conversation with a shorter, different one. This is the
fix for real data loss: reopening a session after a restart could overwrite its history with a
partial copy. A save that would drop stored messages is refused, and the surviving history is
kept.

Attached images survive relocating the data folder, and parked attachments are collected
once nothing refers to them — with the collector refusing to act when it cannot be sure.

A stalled browser sign-in no longer disables device-code login. The wait switched off the
exact remedy the screen recommends.

A rejected agent call says which call failed. The CLI reports some failures — including a
spent weekly plan quota — as a bare JSON-RPC error whose standard name is "Internal error",
and that is all the banner used to show. It now names the call and the code, and keeps the
agent's own reason when there is one.

Correction, added after release. This shipped saying a spent weekly plan quota is
reported that way, and the app suggests checking your usage limits when it happens. That
is wrong. The Grok CLI reports rate limits on their own code (-32003, HTTP 429) with
its own copy about upgrading, and classifies -32603 as a server error specifically
not a rate limit. The hint points at the one thing the CLI would already have told you
about clearly. Fixed on main; the wording inside 0.4.0 itself is misleading.

A turn that fails before the agent says anything no longer leaves a blank message in the
conversation, or on disk.

Reading an older part of a conversation is no longer interrupted by the restore finishing.

The mode and model pickers describe the session in front of you rather than what the next
one would start with, and choosing the option already in force no longer restarts the agent —
which used to replace the conversation with an empty session.

Events are attributed to the session they belong to, so a background session cannot
narrate over the one on screen. The account label never surfaces an email address.

---

Verify a download against SHA256SUMS.txt before running it.

Nightly (d58e159) · post-0.5.0

Unreleased build of main at d58e159, for testing. Not a release. Version string reads 0.5.0 — the app has not been bumped past it.

What is in this that is not in 0.5.0

Every menu button now uses vertical dots (⋮) (#107). A clipped title's trailing "…" could sit beside the old horizontal "⋯" and read as two menu buttons — the likely explanation for #67. The test: if the double button is never seen with this glyph, that was it. If you ever see two ⋮ on one row, report it.

Windows and Linux installers are unsigned; macOS is unsigned and needs right-click → Open. SHA256SUMS.txt covers all six artifacts.

Gronk 0.3.0

Almost all of this is one complaint approached from four directions: Gronk got
slower the longer a conversation ran. The four causes turned out to have nothing
to do with each other.

Fixed

Streaming stopped re-reading the whole conversation on every word. Each token
rebuilt the message list, so every message on screen re-ran its markdown parse —
around 40 ms of parsing per token in a 150-message thread, which is what made the
chat feel like it was seizing. Only the part that actually grew is re-parsed now:
about 0.24 ms for the same token. The agent panel also stopped re-scanning the
transcript on tokens that contained no tool activity, which was a second full
pass on top of the first.

Reopening a session shows you the end of it immediately. The whole transcript
used to render before anything appeared. The last stretch paints first — where you
were reading anyway — and the rest fills in behind without holding the keyboard.
Sessions you have already opened stay in memory, so flipping between two of them
does not re-read either from disk.

Answering a permission prompt no longer rewrites your whole store. The
permission audit lived inside the same file as every saved transcript, so each
decision re-read, re-serialized and re-wrote all of them before the app could
continue. In auto-approve mode that happened on every tool call, not just the ones
you clicked. The audit has its own file now.

The activity chart stopped rebuilding itself after every prompt. It loads when
you visit Home and stays painted when you navigate away.

A wrong "signed in" state can be corrected. If the app believed you were
signed in when you were not, Settings hid both login buttons behind that belief
and there was nothing left to press. Sign-in stays reachable either way, the
sidebar account chip is now a button, and changing the grok binary drops the
cached auth and model answers that were still describing the previous one. Found
and fixed by @0xPBIT.

The selected session row actually highlights. The rule that styled it never
matched the class the row emitted, so the open conversation looked identical to
every other one in the list.

What you get

A scratchpad per project, in the tray above the composer. It belongs to the
folder rather than to a session, so it outlives a project dropping off the recent
list. The tray shows a word count rather than a preview, because that rail is on
screen for the whole session.

Click a day on the activity chart to filter the session list to that day. It
clears with the chip and is not remembered between launches.

The Build panel is the session list — flat and newest-first, with a control to
group by project instead.

The footer says which build you are running, so a bug report can name it.

Verify your download

SHA256SUMS.txt is attached. These installers were built by GitHub Actions from
the commit this tag names; nothing was uploaded from a personal machine.

Known, and honest about it

Every performance figure above was measured on Windows in a test harness, not
by timing a person using the app. The Windows build has been installed and used.

Nobody has run this on macOS or Linux. Both compile and pass the four-platform
test suite, and that is all anyone can currently say about them. The macOS build
is unsigned, so Gatekeeper will object.

The sign-in fix has not been verified on a Mac by anyone, including its author.
It is correct by inspection and it addresses a real defect; whether it resolves
every macOS sign-in problem is unconfirmed.

Gronk 0.2.0

The first full release. Everything before this was a prerelease.

What you get

A right-click menu. Electron ships none, so right-clicking used to do nothing
at all: no cut, copy or paste, and the spelling suggestions Chromium was already
computing sat under the red underline with no way to reach them.

Focus mode. A topbar button, or the [ key, hides the sidebar and idle tray
so the conversation fills the frame.

Agent activity at a glance. A row of dots under the turn that spawned the
work: dim when finished, red when failed, pulsing while running. The tray keeps
the history until you dismiss it, and no longer opens itself while you are
reading.

Fixed

Scrolling stopped fighting you. Scrolling up a line or two while a reply
streamed was undone by the next token, and the end of a turn snapped you back to
the bottom. Both are gone; keyboard and scrollbar scrolling count as intent now
too.

Sign-in state is honest. A successful model list no longer counts as being
signed in, so a fresh install reads as signed out until something actually
indicates an account, and signing out no longer flips straight back.

Tool output stopped filling the screen with image previews. Only tools that
produce images get previews, and the row is capped.

macOS builds ship the Electron and Chromium licences again.

Verify your download

SHA256SUMS.txt is attached. These installers were built by GitHub Actions from
the commit this tag names; nothing was uploaded from a personal machine.

Known, and honest about it

No one has run this on macOS. The mac-specific parts of the sign-in fix are
unit-tested only, and the window controls may need padding. If you are on a Mac
and something looks wrong, that is useful information rather than a surprise.

Visual comparison does not run in CI. The four-platform test matrix does.

Gronk 0.1.9

Tool activity release. Update from any earlier build.

Changed

• Tool activity is a single line you can expand, instead of several things pulsing at once. While Grok worked, the agent fleet indicator and the "Using SHELL" row animated independently, which read as two separate systems doing two separate things. They are now one summary bar showing whatever is actually running, with the detail behind a click.
• Long paths and commands in that bar are shortened to fit. A line that ran past the width of the bar is trimmed rather than pushing the layout around.

Which file do I want?

Platform	File
Windows	Gronk-0.1.9-windows-x64-setup.exe (installer) or -portable.exe
macOS	Gronk-0.1.9-macos-universal.dmg (Apple Silicon and Intel)
Linux	Gronk-0.1.9-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.
• The macOS bundle is currently missing the upstream Electron and Chromium licence files. Attribution for the app's own dependencies ships correctly on every platform; this gap is the runtime's own licences on macOS only, and is being fixed.
• 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.

Gronk 0.1.8

UX and restore release. Update from any earlier build.

Added

• A single session tray above the composer for Plan, Agents, and Usage.
• Command palette (Ctrl/Cmd+K) to jump Home, Chat, Build, settings, and more.
• Pin and remove recent projects from the project menu (remove only forgets the list entry; it never deletes files on disk).
• Opening a project resumes the latest session for that folder. Use New session when you want a blank conversation.
• Chat skeleton while a project or session is opening.
• Allow this kind for session on permission prompts: batch-approve a tool kind for the rest of this agent process without full YOLO.
• OS notifications when the window is unfocused and a permission is needed or a turn finishes.
• First-run onboarding checklist on Home (CLI, sign-in, first project).
• Status menu in the top bar: connection, account, and model in one control.

Changed

• Light theme reworked as paper and ink. The Windows title-bar overlay follows light and dark.
• Wider message column and a tighter top bar.
• Agents tab only appears when something is live.
• Missing images fail more quietly so a bad catalogue cannot own the viewport.
• Session restore paints the local transcript in one shot, then connects the agent.

Which file do I want?

Platform	File
Windows	Gronk-0.1.8-windows-x64-setup.exe (installer) or -portable.exe
macOS	Gronk-0.1.8-macos-universal.dmg, Apple Silicon and Intel
Linux	Gronk-0.1.8-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.

Gronk 0.1.7

Update 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.