> For the complete documentation index, see [llms.txt](https://run-ai-docs.nvidia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://run-ai-docs.nvidia.com/self-hosted/2.23/getting-started/whats-new.md).

# What's New

This section includes release information for the self-hosted version of NVIDIA Run:ai:

* **New Features and Enhancements** - Highlights major updates introduced in each version, including new capabilities, UI improvements, and changes to system behavior.
* **Hotfixes** - Lists patches applied to released versions, including critical fixes and behavior corrections.

{% hint style="info" %}
**Note**

See our [Product version life cycle](/self-hosted/2.23/support-policy/product-version-life-cycle.md) for a list of supported versions and their respective support timelines.
{% endhint %}

## Feature Life Cycle

NVIDIA Run:ai uses life cycle labels to indicate the maturity and stability of features across releases:

* <mark style="color:green;">`Experimental`</mark> - This feature is in early development. It may not be stable and could be removed or changed significantly in future versions. Use with caution.
* <mark style="color:orange;">`Beta`</mark> - This feature is still being developed for official release in a future version and may have some limitations. Use with caution.
* `Legacy` - This feature is scheduled to be removed in future versions. We recommend using alternatives if available. Use only if necessary.


---

# 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://run-ai-docs.nvidia.com/self-hosted/2.23/getting-started/whats-new.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.
