> For the complete documentation index, see [llms.txt](https://ai.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai.ortusbooks.com/introduction/release-history/2.4.0.md).

# 2.4.0

BoxLang AI Module v2.4.0 Release Notes - MiniMax AI Provider, Configuration Security, and Stability Fixes

This release adds support for the MiniMax AI provider, improves configuration security by hiding sensitive data, and includes stability fixes for BoxLang static constructs.

## 🎁 New Features

* **MiniMax AI Provider** - Added support for [MiniMax](https://platform.minimax.io/) AI service with chat, streaming, and embeddings support. Use the `minimax` provider name and set your API key via the `MINIMAX_API_KEY` environment variable.

```javascript
// Using the MiniMax provider
result = aiChat(
    messages: "Hello, how are you?",
    options: { provider: "minimax" }
)

// Or via aiModel()
model = aiModel( provider: "minimax", params: { model: "MiniMax-Text-01" } )
```

## 🔧 Enhancements

* **Secure `getConfig()` Output** - Updated `getConfig()` to redact sensitive information such as API keys from the returned configuration struct.

## 🐛 Bug Fixes

* **BoxLang Static Constructs** - Replaced inline static constructs with proper BoxLang static references to avoid compatibility issues with newer BoxLang versions.


---

# 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://ai.ortusbooks.com/introduction/release-history/2.4.0.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.
