0.17.0

0.17.0 (2026-08-16)

Fixed: an answer appearing two or three times

If you came back to a conversation shortly after it finished generating, the reply could land in it again. Come back twice and you had three copies.

A finished generation is kept on the server for a few minutes so a tab that was closed mid-answer can still pick it up. Revisiting the conversation inside that window replayed it from the start, and the tab that had already watched it live applied the whole thing a second time.

Every message a generation produces now carries the moment it was created, stamped once and never rewritten, so the same answer delivered twice is recognised and stored once. Same for compaction markers, which had the same problem and would have drawn two boundaries where there is one.

One thing to do yourself: copies already in your conversations stay there. Delete the extra ones by hand, they will not come back (hopefully !).

Bug Fixes

• chat: lay the composer's mention overlay out as text, not as a flex row (ddd4b73)
• chat: stop the composer's mention overlay from rendering its own indentation (8d6dcbd)
• chat: stop the conversation fighting you when you scroll during a generation (1dd4ccd)
• runs: apply a replayed answer once, so revisiting a conversation stops duplicating it (ea5c1a5)

Features

• admin: show when each account was last around, in the users list (5fbb296)
• chat: delete a single message, which the conversation had no way to do (19ca0a1)

Performance Improvements

• admin: let the statement do the throttling too, so a restart costs nothing (a5eeb2f)