> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/release-notes/2025/february-2025.md).

# February 2025

## February 24th, 2025

## Improvements

### Video Quality

Changes to **video encoding** to stream better quality videos when good bandwidth available.

### Mobile Improvements - Msngr Plus

We have improved the mobile experience for Msngr Plus, ensuring smoother navigation and improved usability when accessing the channel during an exercise.

#### Key Mobile Improvements:

* **Optimized Main View**: Improved interface when users enter the channel for a more intuitive experience.
* **Enhanced Chat Functionality**:
  * **Impersonation**: Improved switching between personas.
  * **Better Navigation**: Streamlined chat interactions for efficiency.
* **Chat Details Access**:
  * Users can now tap on the upper bar (persona/group name) to access chat details, similar to WhatsApp.
  * **Improved Member Management**: Easier member removal options.

### Social Watch

**Social Watch** channel improvements to UX to prompt first time uses to enter a watch word or phrase.

## Other fixes

Minor bug fixes.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpdocs.conducttr.com/release-notes/2025/february-2025.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.