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.
