The performance release. Two changes, both about what happens when you have been using the same install for a month.
History storage rewritten. Previously the chat list was one file that grew with every session.
Now each session is its own file, with an index.json describing them, so opening the app reads an
index instead of everything. It also makes a corrupt session a single session, not the whole list.
The migration path is handled, and the legacy chats.json is kept readable, with a later release
trimming a deleted chat out of the seed so it cannot resurrect itself.
The render cache. Long conversations were being re-rendered from scratch when new content arrived, which is O(n²): every new message re-drew everything. With the cache it is O(n). The changelog calls it a "big speedup for long conversations", and it is. An agent that has run 400 tool calls in a session is not an edge case in this product; it is Tuesday.
Sidebar performance is in here as well, which is the surface where the cost of a big history shows up first.
Worth noting the pattern in this project's history: features make chats longer, and longer chats make the storage and rendering costs visible, and so every few releases the plumbing under the chat view gets rebuilt. This is the first time that happened, and 1.12.1's "mid-turn history save is best-effort" is the most recent.