When a message has a saved (kept) image, changing any of the metadata fields like "hidden from AI", "hidden from user", etc. can sometimes cause the saved image to disappear and show as blank. Editing the message text itself seems fine, it's specifically the behind-the-scenes fields that trigger it. The saved image data is still in the database (in customData.__savedImages), keyed by the exact prompt string including the uniqueness tag ((img0:0), (img1:0), etc.). Something in the re-render flow after a metadata update seems to strip or mismatch that key, so the image lookup fails. Worth checking around line 6672 where (imgN:0) tags get stripped for AI context. if that stripping somehow touches the stored message string rather than just a copy, the key would no longer match what's saved in __savedImages. This bug might seem unlikely to hit in normal usage, but there's a pretty natural scenario where it comes up. Say someone generates an image with the intention of deleting it later, but the generation comes out perfect by luck. They decide to keep it but also want to hide the message from the AI so it doesn't see it in the chat context. So it's not a common occurrence. To reproduce: generate an image, keep it, then change any hiddenFrom option on that message and confirm. Sometimes the image will be gone.

Side note: also noticed that clicking the 🖼️ Image button sometimes generates images with a completely empty prompt (example of what gets stored: (img1:0)), resulting in random unrelated images. Didn't check exact cause.