Images, done properly. There have been four releases of image work in this history (1.3.11 preprocessing, 1.6.0 attach and render, 1.7.0 local file URLs, and this), and 1.8.3 is the one that makes them durable.
Content-addressed attachments. An attached image is stored by the hash of its bytes, not by a filename in a temp directory. That has three consequences that matter: the same image attached twice is one copy, an attachment survives a restart and a chat reload, and a saved chat can be re-opened later with the image still in it. Temp files do none of those.
Every input path works. Clipboard paste, drag and drop, a file picker, and a path typed into a prompt. The failure mode before this was specific and annoying: an image that worked in the live conversation disappeared when the chat was reloaded, because the live path kept it in memory and the saved path did not.
1.8.2 is the release before this one, and it contains nothing but version numbers. The
changelog says it plainly: version bump to keep the three editions in lockstep, no functional
change. The C++ and Rust editions ship on their own release trains, and when the Python edition moves
ahead the shared contract gets out of step. A version-only release is the mechanism for getting it
back in step, and this log lists it as 1.8.2 with the 1.8.3 post covering the pair.