#
Ekorbia v0.2 — chat groups & comparison mode
Ekorbia 0.2.0 is out with two new significant new features and a couple of quality-of-life improvements.
Chat groups (sidebar folders) #
The history sidebar used to be flat with date buckets: Today, Yesterday, This week.
0.2.0 adds user-defined folders that sit above the date buckets:
Click + New group at the top of the sidebar to create one. - Drag any chat onto a folder header to file it. - Drag it back into a date section to unfile. - Right-click a chat for a context menu (rename, move, delete).
Groups are intentionally one level deep — no nested folders.
Compare 2-3 models side-by-side #
A new comparison-chat mode. Click the columns icon in the sidebar, pick 2 or 3 installed models, send one prompt — every model streams its response into an adjacent column in parallel. When you find the answer you want, click ✓ Keep this on that column.
Three things happen on Keep:
- The chat transitions from compare mode to a normal single-model chat.
- The kept model becomes the chat's active model — follow-ups go to it.
The unpicked responses are preserved under a ▸ N alternatives disclosure on the kept message, so the comparison stays inspectable later.
It's deliberately a one-turn experience. If you want to keep comparing you start a new compare chat. The full walkthrough — including how the per-column Stop button works, what to do if one model errors out, and the VRAM gotchas when picking three large models — is in the
docs. Caveat: attachments aren't supported in compare mode yet. Files, folders, and the memory file are skipped for comparison sends. Prompts attach normally.
Model + tokens footer on every assistant message #
A subtle monospace line at the bottom of every assistant reply now shows which model produced the response and the token counts (prompt / completion / total). If you switched models mid-conversation, scrolling back through the chat now makes attribution obvious — no more "wait, which one wrote that?"
Under the hood: database migrations #
For the engineers: 0.2.0 introduces an
`apply_migrations()`
step in
db.rs
that runs after
execute_batch(SCHEMA)
, using
ALTER TABLE ADD COLUMN
for any new columns
on upgraded installs. It's idempotent via
PRAGMA
introspection, so fresh installs no-op through it and upgrades pick up the new columns cleanly.
Practical effect: from 0.2.0 onward, schema changes can ship without users having to delete their database. The chat groups and compare-mode features both rely on this — it'd have been substantially harder to ship them otherwise.
How to get it #
The
releases page
has the .dmg
. Existing 0.1.x users: the first launch will run the migration silently, no action on your part.