> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/desktop/keeperchat/older/keeperchat-client-release-4.5.0.md). # KeeperChat Client Release 4.5.0 ## Bug Fixes * CC-1820: Self-Destruct messages not hidden in chat list panel on Windows * CC-1494: Contacts created when invalid phone numbers added * CC-1763: Changed text from Keeper Vault to KeeperChat in DNA setup * CC-1826: Prevent sending empty messages on iOS * CC-1497: Fixed issue with avatar removal when deleting messages on Windows * CC-1721: Allow to use more than 1 word in First/Last name when editing contacts on Mac * CC-1855: Fixed crash on Mac and Windows when a contact phone number is longer than 10 digits ## Features and Improvements * CC-1642: Close list of options of attachments by clicking outside of it on Windows --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.keeper.io/release-notes/desktop/keeperchat/older/keeperchat-client-release-4.5.0.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.