A chat view that no longer flickers
Streaming responses had a cluster of distracting glitches at the seam between the live, optimistic view and the saved version: send a follow-up and your new message plus the previous reply would briefly vanish while loading; the first reply showed two stacked "thinking" animations with a visible page jolt; and very often the finished reply would blink out and flash back the instant streaming ended. Your own message bubble double-faded on every follow-up too. These all traced to one root cause — the saved message re-running its entrance animation when it took over from the live streaming view — and they are now gone, across fast replies, long reasoning, and tool-call turns.
No more random "Job not found"
When the local backend restarted mid-conversation — a watchdog restart after repeated health failures, or a crash — the app popped an alarming "Job not found" error while trying to reconnect to streams the fresh backend no longer knew about. The stream registry now reconciles surviving streams against the restarted backend's active-job list — resuming what is still running, re-attaching where the job moved, and quietly finalizing the rest from your saved history — with no scary toast. No data was ever lost; now it is silent too.
Renaming a chat is discoverable again
The rename entry point is back: open a chat row's ••• overflow menu, or just double-click the title, to rename it inline. Single-click navigation is debounced so it no longer fights the double-click.
Quieter image attachments and visible thinking
Attaching an image to a model that cannot read images now warns you up front — an inline notice on the composer and a clearer attach affordance — instead of silently failing at send time. And reasoning from providers that stream reasoning_content is echoed back to the client again, so the model's thinking shows up instead of being dropped.