> For the complete documentation index, see [llms.txt](https://docs.mluvii.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mluvii.com/en/updates-mluvii/archive/2.72.md). # 2.72 Deployed on: 24. 08. 2021 ## **Mluvii News** ### 1) **Information about groups via API** You simply get information about groups, their id and name via API. ### 2) **View files directly in the chat** With a single click, you can now view files directly in the chat and browse between them, from the perspective of both the operator and the client. #### **Minor changes in the application:** * .Webp files are already appearing in chat * The camera and microphone buttons are displayed correctly during an AV call on Android / Chrome * HTML export sessions in which was the chatbot are displayed correctly * The routing visualization correctly displays arrows between elements * Images and files are displayed in the chat history (past sessions) * Searching the table of all sessions now handle spaces at the end of rows correctly **Thank you for your feedback, which helps us to improve mluvii. :)** --- # 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.mluvii.com/en/updates-mluvii/archive/2.72.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.