# Helvia.ai Release 5.56.0

Our latest release, taking place on 30 May 2024, focuses mainly on console optimization, along with UX improvements. Read on to learn more about each update.

### 1. Improved UX with sticky buttons on the console

We have enhanced the user experience of the console by making the Add/Save buttons sticky. This means that the buttons will always be visible when scrolling through forms, tables, and other elements. With this improvement, console editors can easily access make edits without having to scroll back up the page.

<figure><img src="https://1873349521-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsBKCPTKnYrr0QVmp6Jo5%2Fuploads%2FrHV35N51cCHFw00ajCRx%2Fimage.png?alt=media&#x26;token=2ac444ea-51ca-434e-a4d8-29714c60033a" alt="" width="463"><figcaption></figcaption></figure>

### 2. Streamlined bot set up process

We have removed the LiveChat powerup from the console to streamline the bot setup process. This eliminates an extra step and simplifies the setup process, improving the efficiency of bot creation. [LiveChat settings](https://docs.helvia.ai/chatbricks-release-notes/helvia.ai-release-5.55.0#id-1.-improved-livechat-settings-ux) have already been moved to the bot plugin settings, further improving the user experience.

### 3. Organizing imported KB articles into named groups

When importing articles to a knowledge base, ChatBricks now automatically groups them under a new group related to the imported file. This feature allows you to easily distinguish which articles came from which file, making it easier to manage and organize your knowledge base.


---

# Agent Instructions: 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:

```
GET https://docs.helvia.ai/resources/release-notes/2024/helvia.ai-release-5.56.0.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.