diff --git a/content/en/docs/apidocs-mxsdk/apidocs/deployment/backups-api-v2.md b/content/en/docs/apidocs-mxsdk/apidocs/deployment/backups-api-v2.md
index 8ea4cc38fb9..fa478d6d9e6 100644
--- a/content/en/docs/apidocs-mxsdk/apidocs/deployment/backups-api-v2.md
+++ b/content/en/docs/apidocs-mxsdk/apidocs/deployment/backups-api-v2.md
@@ -68,7 +68,7 @@ To perform an action via the Backups API, you need **Backups Access** and **API
To download a backup of your data, do as follows:
-1. Make sure that you have an API key or a PAT, and the **API Access** and **Backups** permissions.
+1. Make sure that you have an API key and the **API Access** and **Backups** permissions.
2. If the snapshot already exists, find the [snapshot ID](/developerportal/operate/backups/#backups-details).
diff --git a/content/en/docs/community-tools/contribute-to-mendix-docs/style-guide/product-naming-guide.md b/content/en/docs/community-tools/contribute-to-mendix-docs/style-guide/product-naming-guide.md
index 158196d396e..00b9599e7c4 100644
--- a/content/en/docs/community-tools/contribute-to-mendix-docs/style-guide/product-naming-guide.md
+++ b/content/en/docs/community-tools/contribute-to-mendix-docs/style-guide/product-naming-guide.md
@@ -246,7 +246,7 @@ For specific Maia features, use the feature name directly: Logic Recommender, Wo
It is okay to include "Maia" as part of the feature name if it is introduced for the first time or if no near context about Maia is given: Maia Logic Recommender, Maia Workflow Recommender, Maia Translation Generator, for instance.
-As of Studio Pro 11.8, Maia Make replaces Maia's individual features. Refer to "Maia" or "Maia Make" as a set of capabilities. Do not refer to older individual tools, such as "Maia Chat", "Maia for Domain Models", or "Maia for Pages" unless referring to Studio Pro 11.7 and below.
+Maia Chat is an exception: use "Maia Chat" instead of "Chat". Only use "Chat" in very rare cases: as a page title in the left navigation menu under the [Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/) category.
Capitalize in all instances.
diff --git a/content/en/docs/deployment/mendix-cloud-deploy/deploy-apis-with-ai-agents.md b/content/en/docs/deployment/mendix-cloud-deploy/deploy-apis-with-ai-agents.md
index 3296e9145e0..5a487676294 100644
--- a/content/en/docs/deployment/mendix-cloud-deploy/deploy-apis-with-ai-agents.md
+++ b/content/en/docs/deployment/mendix-cloud-deploy/deploy-apis-with-ai-agents.md
@@ -13,7 +13,7 @@ description: "Describes how to connect AI coding assistants to Mendix Cloud usin
For example, you can ask the AI assistant to list your apps, deploy the latest package to an acceptance environment, or stop a production environment, without writing `curl` commands or navigating the Mendix Portal.
{{% alert color="warning" %}}
-The use of AI tools is non-deterministic, outputs may vary between runs. AI Assistants/Agents will have permissions based on what the Personal Access Token (PAT) has access to. Through the [Backups API](/apidocs-mxsdk/apidocs/backups-api/) and [Logs](/developerportal/operate/logs/), they may have access to production environments and Personally Identifiable Information (PII) contained within your environments. Carefully review and limit the scope of credentials before use.
+The use of AI tools is non-deterministic, outputs may vary between runs. AI Assistants/Agents will have permissions based on what the API Key and Personal Access Token (PAT) have access to. Through the [Backups API](/apidocs-mxsdk/apidocs/backups-api/) and [Logs](/developerportal/operate/logs/), they may have access to production environments and Personally Identifiable Information (PII) contained within your environments. Carefully review and limit the scope of credentials before use.
{{% /alert %}}
## Prerequisites
@@ -21,7 +21,9 @@ The use of AI tools is non-deterministic, outputs may vary between runs. AI Assi
Before you start, make sure you have the following:
* An MCP-compatible AI client that supports custom request headers, such as Claude Code or VS Code with GitHub Copilot
+* A Mendix account with API access enabled
* A [Personal Access Token (PAT)](/portal/user-settings/#pat) with the `mx:deployment:write` and `mx:deployment:read` scopes selected
+* A [Mendix API key](/portal/user-settings/#profile-api-keys)
## Connecting Your AI Assistant {#connecting}
@@ -32,10 +34,16 @@ To add the Mendix MCP server in Claude Code, run the following command in your t
```bash
claude mcp add --scope user --transport http mendix-cloud-mcp \
https://mcp.home.mendix.com/ \
---header "Authorization: MxToken {GENERATED_PAT}"
+--header "Authorization: MxToken {GENERATED_PAT}" \
+--header "Mendix-Username: {Mendix-Username}" \
+--header "Mendix-ApiKey: {Mendix-ApiKey}"
```
-Replace `{GENERATED_PAT}` with your Mendix Personal Access Token (PAT).
+Replace the following placeholders with your credentials:
+
+* `{GENERATED_PAT}` – the generated Mendix Personal Access Token (PAT)
+* `{Mendix-Username}` – the login name of the user making the request, with the required privileges in the Mendix Platform
+* `{Mendix-ApiKey}` – the API key associated with that user
To verify the connection, run the following command:
@@ -54,6 +62,8 @@ mendix-cloud-mcp:
URL: https://mcp.home.mendix.com/
Headers:
Authorization: MxToken {GENERATED_PAT}
+ Mendix-Username: {Mendix-Username}
+ Mendix-ApiKey: {Mendix-ApiKey}
To remove this server, run: claude mcp remove mendix-cloud-mcp -s user
```
@@ -70,7 +80,9 @@ To add the Mendix MCP server in VS Code, add the following configuration to your
"type":"http",
"url":"https://mcp.home.mendix.com/",
"headers":{
- "Authorization":"MxToken {GENERATED_PAT}"
+ "Authorization":"MxToken {GENERATED_PAT}",
+ "Mendix-Username":"{Mendix-Username}",
+ "Mendix-ApiKey":"{Mendix-ApiKey}"
}
}
}
@@ -78,7 +90,7 @@ To add the Mendix MCP server in VS Code, add the following configuration to your
}
```
-Replace `{GENERATED_PAT}` with your Mendix Personal Access Token (PAT).
+Replace the placeholder values with your credentials as described in the [Claude Code](#claude-code) section above.
## Available Capabilities {#capabilities}
@@ -137,10 +149,15 @@ Once connected, your AI assistant has access to the following capabilities.
Your credentials are passed directly to the Mendix APIs and are not stored or inspected by the MCP gateway. Each user authenticates using their own credentials.
-All APIs, including the Deploy API, Build API, Backups API, and App Permissions, use the `Authorization: MxToken {GENERATED_PAT}` header.
+Two authentication methods are used depending on the API:
+
+| API Version | Headers Required |
+| --- | --- |
+| Deploy API v4, App Permissions | `Authorization: MxToken {GENERATED_PAT}` |
+| Deploy API v1/v2, Build API, Backups API | `Mendix-Username` and `Mendix-ApiKey` |
{{% alert color="info" %}}
-Include the `Authorization` header in your connection configuration to ensure all tools work correctly.
+Include all three headers in your connection configuration to ensure all tools work correctly.
{{% /alert %}}
## Client Compatibility {#compatibility}
@@ -148,7 +165,7 @@ Include the `Authorization` header in your connection configuration to ensure al
The Mendix MCP integration works with any MCP-compatible client that supports HTTP transport (streamable HTTP) and custom headers for authentication.
{{% alert color="warning" %}}
-Clients that only support OAuth 2.0 authentication without custom header support are not compatible with the Mendix Cloud MCP integration, as Mendix APIs use token-based authentication.
+Clients that only support OAuth 2.0 authentication without custom header support are not compatible with the Mendix Cloud MCP integration, as Mendix APIs use token and API key-based authentication.
{{% /alert %}}
## Known Limitations {#limitations}
@@ -170,7 +187,7 @@ The following limitations apply:
### 401 Unauthorized
-Your credentials are incorrect or have expired. Regenerate your PAT.
+Your credentials are incorrect or have expired. Regenerate your PAT and verify that your API key is still active.
### 403 Forbidden
@@ -184,7 +201,9 @@ Your MCP client is not sending the correct `Accept` header. This happens when yo
claude mcp remove mendix-cloud-mcp
claude mcp add --scope user --transport http mendix-cloud-mcp \
https://mcp.home.mendix.com/ \
---header "Authorization: MxToken {GENERATED_PAT}"
+--header "Authorization: MxToken {GENERATED_PAT}" \
+--header "Mendix-Username: {Mendix-Username}" \
+--header "Mendix-ApiKey: {Mendix-ApiKey}"
```
### Tools Not Showing Up
diff --git a/content/en/docs/deployment/mendix-cloud-deploy/maia-operate/_index.md b/content/en/docs/deployment/mendix-cloud-deploy/maia-operate/_index.md
index fbed244431a..1d2e1eca318 100644
--- a/content/en/docs/deployment/mendix-cloud-deploy/maia-operate/_index.md
+++ b/content/en/docs/deployment/mendix-cloud-deploy/maia-operate/_index.md
@@ -9,8 +9,8 @@ description_list: true
## Introduction
-Operating a production application requires continuous monitoring of its health and behavior, including reviewing logs, investigating errors, and understanding application activity over time. Maia Operate simplifies these tasks by using data already available in Mendix Cloud to provide AI-powered insights into your running application. It helps you resolve incidents faster and spend less time on investigation and routine operational work.
+Operating a production application requires continuous monitoring of its health and behavior. This often involves reviewing logs, investigating errors, and understanding application activity over time.
-Maia Operate covers the operation stage of the application lifecycle. Insights from operating your app can become input for the next iteration, which you can plan in Mendix Portal and build in Studio Pro with Maia. For an overview of how Maia supports each stage, see [Maia Across the Development Lifecycle](/refguide/maia-development-lifecycle/).
+Maia Operate simplifies these operational tasks by using data already available in Mendix Cloud to provide AI-powered insights into your running application. It helps you resolve incidents more quickly, reduce investigation time, and spend less effort on routine operational work.
## Documents in This Category
diff --git a/content/en/docs/developerportal/maia-plan/_index.md b/content/en/docs/developerportal/maia-plan/_index.md
index fd8eee84f6f..002374fe8c4 100644
--- a/content/en/docs/developerportal/maia-plan/_index.md
+++ b/content/en/docs/developerportal/maia-plan/_index.md
@@ -13,6 +13,4 @@ Maia Plan helps you create a detailed project plan, based on which you can then
{{< figure src="/attachments/developerportal/maia/maia-create-app.png" alt="Plan and build with Maia entry point" max-width=50% >}}
-Maia Plan covers the planning stage of the application lifecycle. You can use the stories from the plan as input when building your app in Studio Pro with Maia Make, or have external AI agents read the plan through [Maia Plan as MCP Server](/developerportal/maia-plan-mcp/). For an overview of how Maia supports each stage, see [Maia Across the Development Lifecycle](/refguide/maia-development-lifecycle/).
-
## Documents in This Category
diff --git a/content/en/docs/marketplace/marketplace-home-page.md b/content/en/docs/marketplace/marketplace-home-page.md
index fa40ecdaabc..3e96daffed6 100644
--- a/content/en/docs/marketplace/marketplace-home-page.md
+++ b/content/en/docs/marketplace/marketplace-home-page.md
@@ -145,6 +145,7 @@ This table breaks down the roles and permissions for content groups:
| Group Admin | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| Group Member | ✘ | ✘ | ✘ | ✔ | ✔ | ✔ | ✔ |
| Organization member (not part of any group) | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ |
+| Guest | ✘ | ✘ | ✘ | ✘ | ✔ | ✘ | ✘ |
| Developer (not part of any group) | ✘ | ✘ | ✘ | ✔ | ✔ | ✔ | ✔ |
### Content Tab {#group-content}
diff --git a/content/en/docs/mendix-portal/maia-portal.md b/content/en/docs/mendix-portal/maia-portal.md
index dcfa0398f75..f40a437ff92 100644
--- a/content/en/docs/mendix-portal/maia-portal.md
+++ b/content/en/docs/mendix-portal/maia-portal.md
@@ -11,9 +11,7 @@ aliases:
Mendix AI Assistance (Maia) refers to Mendix Platform capabilities that leverage [artificial intelligence (AI)](https://www.mendix.com/glossary/artificial-intelligence-ai/) and [machine learning (ML)](https://www.mendix.com/glossary/machine-learning/) to assist developers in application development. Maia is designed to help development teams in modeling and delivering Mendix applications faster, more consistently, and with higher quality.
-{{< figure src="/attachments/developerportal/global-nav/maia-mendix-portal.jpg" alt="Maia in Mendix Portal" width="500" >}}
-
-Maia in Mendix Portal supports the planning, collaboration, and feedback stages of the application lifecycle. For example, you can use Maia Plan to define the scope of a new app, then continue in Studio Pro with Maia Make to build it. For an overview of how Maia supports each stage, see [Maia Across the Development Lifecycle](/refguide/maia-development-lifecycle/).
+{{< figure src="/attachments/developerportal/global-nav/maia-mendix-portal.jpg" width="500" >}}
## Maia Capabilities in Mendix Portal
@@ -51,7 +49,7 @@ Maia Chat does not use any project, customer, or company information. It only us
Maia Chat is a built-in chat interface in the Mendix Platform powered by Generative AI. Developers can ask questions about all aspects of Mendix, including how to apply concepts, best practices, governance tools, and development patterns.
-Maia Chat is also available in Studio Pro 10.12.0 to 11.7. In Studio Pro 11.8 and above, Maia Chat is part of Maia Make, where you can ask questions directly to Maia in the **Chat** tab. For more information, see [Chat with Maia](/refguide/maia-chat/).
+Maia Chat is also available in Studio Pro 10.12.0 and above. See [Maia Chat](/refguide/maia-chat/) for more information.
For information on Mendix data storage policies and practices for Maia, see [Maia Privacy Policy](https://www.mendix.com/legal/privacy/maia/).
diff --git a/content/en/docs/private-platform/pmp-maia.md b/content/en/docs/private-platform/pmp-maia.md
index d53f4351278..879259d290c 100644
--- a/content/en/docs/private-platform/pmp-maia.md
+++ b/content/en/docs/private-platform/pmp-maia.md
@@ -9,8 +9,6 @@ weight: 51
Mendix AI Assistance (Maia) refers to Mendix Platform capabilities that leverage [artificial intelligence (AI)](https://www.mendix.com/glossary/artificial-intelligence-ai/) and [machine learning (ML)](https://www.mendix.com/glossary/machine-learning/) to assist developers in application development. Maia is designed to help development teams in modeling and delivering Mendix applications faster, more consistently, and with higher quality.
-For an overview of how Maia supports each stage of the application lifecycle, see [Maia Across the Development Lifecycle](/refguide/maia-development-lifecycle/). Not all capabilities on that page are available in Private Mendix Platform. The following section lists the capabilities that are supported.
-
## Maia Capabilities in Private Mendix Platform
Mendix AI Assistance (Maia) in Private Mendix Platform has the following capabilities:
@@ -18,7 +16,7 @@ Mendix AI Assistance (Maia) in Private Mendix Platform has the following capabil
Starting point for app creation:
* **Start with Maia** - a starting point in Studio Pro that helps you to start the app development process. Based on a required text description and an optional image or PDF, it generates an app that includes a domain model, data management overview pages, test data, and a tailored homepage. For more information, see [Start with Maia](/refguide/start-with-maia/).
-* **Maia Make** - a unified conversational interface in Studio Pro that groups all agentic development capabilities into a single chat experience. With this interface, everything happens in one place. Start a conversation, describe what you need, and Maia generates the necessary app artifacts, such as a new domain model, pages, and microflows. You can also ask it to explain documents for you, including your app logic and pages. For more information, see [Maia Make Capabilities](/refguide/maia-make/).
+* **Maia Make** - a unified conversational interface in Studio Pro that groups all AI-assisted development capabilities into a single chat experience. With this interface, everything happens in one place. Start a conversation, describe what you need, and Maia generates the necessary app artifacts, such as a new domain model, pages, and microflows. You can also ask it to explain documents for you, including your app logic and pages. For more information, see [Maia Make Capabilities](/refguide/maia-make/).
Recommenders:
@@ -28,15 +26,15 @@ Recommenders:
Generators:
-* **Domain Models in Maia Make** – helps you generate new [domain models](/refguide/domain-model/), and explain and provide suggestions for existing domain models. For more information, see [Domain Models in Maia Make](/refguide/maia-for-domain-model/).
+* **Maia for Domain Model** – helps you generate new [domain models](/refguide/domain-model/), and explain and provide suggestions for existing domain models. For more information, see [Maia for Domain Model](/refguide/maia-for-domain-model/).
For Private Mendix Platform, this feature is supported for version 11.6 and newer.
-* **Pages in Maia Make** – helps you generate a [page](/refguide/page/). It helps you add and configure widgets based on a text input and an optional image. After a page is generated, you can continue in the same session to ask Maia for further improvements and explanations. For more information, see [Pages in Maia Make](/refguide/maia-for-pages/).
+* **Maia for Pages** – helps you generate a [page](/refguide/page/). It helps you add and configure widgets based on a text input and an optional image. After a page is generated, you can continue in the same session to ask Maia for further improvements and explanations. For more information, see [Maia for Pages](/refguide/maia-for-pages/).
For Private Mendix Platform, this feature is supported for version 11.6 and newer.
-* **Workflows in Maia Make** – helps you generate a [Workflow](/refguide/workflows/). By providing a use case via text input or an image, Maia can help you start creating your workflows. For more information, see [Workflows in Maia Make](/refguide/maia-for-workflows/).
+* **Maia for Workflows** – helps you generate a [Workflow](/refguide/workflows/). By providing a use case via text input or an image, Maia can help you start creating your workflows. For more information, see [Maia for Workflows](/refguide/maia-for-workflows/).
* **Validation Assist** – helps you build validation microflows in a more automated way using pre-built expressions. For more information, see [Validation Assist](/refguide/validation-assist/).
## Changing the LLM Provider for Maia
@@ -61,9 +59,9 @@ The following table shows which Maia capabilities are supported by various model
| Maia Capability | AWS Bedrock | Anthropic | Azure | OpenAI |
| --- | --- | --- | --- | --- |
-| **Pages in Maia Make** | Full support | Full support | Simple requests only | Simple requests only |
-| **Domain Models in Maia Make** | Full support | Full support | Full support | Full support |
-| **Workflows in Maia Make** | Full support | Full support | Simple requests only | Does not support workflow creation |
+| **Maia for Pages** | Full support | Full support | Simple requests only | Simple requests only |
+| **Maia for Domain Model** | Full support | Full support | Full support | Full support |
+| **Maia for Workflows** | Full support | Full support | Simple requests only | Does not support workflow creation |
| **Start with Maia** | Full support | Full support | Full support | Full support |
| **Best Practice Recommender** | Full support | Full support | Full support | Full support |
| **UI Recommender** | Full support | Full support | Full support | Full support |
diff --git a/content/en/docs/private-platform/quickstart/pmp-quickstart.md b/content/en/docs/private-platform/quickstart/pmp-quickstart.md
index c21ed573bc5..106e2c63198 100644
--- a/content/en/docs/private-platform/quickstart/pmp-quickstart.md
+++ b/content/en/docs/private-platform/quickstart/pmp-quickstart.md
@@ -545,7 +545,7 @@ Install the Private Mendix Platform by doing the following steps:
## Installing Maia for the Private Mendix Platform {#maia}
-[Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/) refers to Mendix Platform capabilities that leverage [artificial intelligence (AI)](https://www.mendix.com/glossary/artificial-intelligence-ai/) and [machine learning (ML)](https://www.mendix.com/glossary/machine-learning/) to assist developers in application development. Private Mendix Platform currently offers support for Maia-assisted app creation. Other Maia capabilities will be made available in future releases.
+[Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/) refers to Mendix Platform capabilities that leverage [artificial intelligence (AI)](https://www.mendix.com/glossary/artificial-intelligence-ai/) and [machine learning (ML)](https://www.mendix.com/glossary/machine-learning/) to assist developers in application development. Private Mendix Platform currently offers support for Maia-assisted app creation. Other Maia capabilities, such as Maia Chat, will be made available in future releases.
To enable [Maia for Private Mendix Platform](/private-mendix-platform/maia/), perform the following steps:
diff --git a/content/en/docs/quickstarts/responsive-web-app.md b/content/en/docs/quickstarts/responsive-web-app.md
index 0aeac9317b1..6be56b5e7d5 100644
--- a/content/en/docs/quickstarts/responsive-web-app.md
+++ b/content/en/docs/quickstarts/responsive-web-app.md
@@ -88,11 +88,11 @@ The top bar includes several key elements:
**At the center of the screen** is the **working area**, where you'll see the currently open document tab. It's the main space within the IDE where you design, model, and configure application components visually. Think of it as the code editor in a text-based programming IDE.
{{% alert type="info" %}}
-When you launch **Studio Pro** for the first time, you’ll see the **Welcome** tab. From here, you can access:
+When you launch **Studio Pro** for the first time, you’ll see the **Welcom** tab. From here, you can access:
* [Maia Learn](/refguide/maia-learn/) – learning materials to help you get started
-* [Maia Make](/refguide/maia-make/) – a group of agentic development capabilities in Studio Pro where you can describe your app requirements and get quick answers, support, and guidance in one conversation
+* [Maia Chat](/refguide/maia-chat/) – an AI-powered assistant for quick support and guidance
We recommend watching the introduction videos to get familiar with the basic concepts of Mendix development before you start building your app.
{{% /alert %}}
@@ -145,11 +145,11 @@ You have created a new persistable entity called **Employee**. This means the en
{{< figure src="/attachments/quickstarts/part1/7.2 CreateAttributes.png" width="450px" alt="Create attributes on an entity">}}
{{% alert type="info" %}}
-You can also create a domain model by describing your application to Maia. Maia generates the domain model based on your input. For more information, see [Domain Models in Maia Make](/refguide/maia-for-domain-model/).
+You can create a domain model by simply describing your application using [Maia for Domain Model](/refguide/maia-for-domain-model/) an AI-powered tool that generates domain models based on your input.
-To use it in Studio Pro 11.8 and above, open the **View** menu and select the **Maia** pane, then describe your application in the chat. In Studio Pro 11.7 and below, click **Maia for Domain Model** in the **Working Area**, then describe your application in the chat box on the right.
+To use it, **click Maia for Domain Model** in the **Working Area**, then describe your application in the chat box on the right.
-In this case, you can ask Maia: “Create a domain model that stores employee information: first name, last name, job role, and employee ID.”
+In our case, you can ask Maia: “Create a domain model that stores employee information: first name, last name, job role, and employee ID.”
{{% /alert %}}
### Add an Association
@@ -258,9 +258,9 @@ To deploy your app to the Mendix Cloud (Paid), there are multiple options for ho
Throughout this guide, you built your **Employee** app by hand—dragging entities onto the canvas, wiring up buttons, and writing microflow logic step by step. That is a great way to learn how Studio Pro works under the hood. But once you are comfortable with the basics, you do not have to do everything manually. Maia, Mendix's built-in AI assistant, can take over much of this repetitive modeling work for you.
-Unlike a traditional chatbot that only answers questions, Maia is agentic: it can use your app's existing domain model, pages, and logic as context to create or modify elements directly in Studio Pro. Through [Maia Make](/refguide/maia-make/), you can describe what you want in plain language, and Maia generates artifacts such as domain models, pages, microflows, workflows, and OQL queries. In the same conversation, you can ask development questions or use [Maia Explain](/refguide/maia-explain/) to understand existing functionality without changing your app.
+Unlike a typical chatbot that only answers questions, Maia is agentic: it can read your app's current domain model, pages, and logic, understand the context you are working in, and then directly create or modify app elements on your behalf. Ask it to add an entity, generate a page, or build out a microflow, and it will produce real, editable Studio Pro artifacts—not just a suggestion or a code snippet for you to copy in.
-Studio Pro also includes recommenders that the next best widget or microflow activity as you build. For more advanced use cases, [Maia Agent Skills](/refguide/maia-agent-skills/) and [Agent Instructions](/refguide/maia-agent-instructions/) let you tailor Maia to your team's conventions, helping it produce suggestions that align with how your organization builds apps.
+Maia is not one single feature but a collection of capabilities woven into Studio Pro. [Maia Make](/refguide/mendix-ai-assistance/), is a conversational interface where you describe what you want in plain language and Maia generates the domain model changes, pages, or microflows to match. Within Maia Make are focused generators (for domain models, pages, workflows, and OQL queries), recommenders that suggest the next best widget or microflow activity as you build, and guidance tools like [Maia Chat](/refguide/maia-chat/) and [Maia Explain](/refguide/mendix-ai-assistance/) for when you want an explanation rather than a change to your app. As you grow more advanced, [Maia Agent Skills](/refguide/maia-agent-skills/) and Agent Instructions let you teach Maia your team's own conventions so Maia's suggestions stay consistent with how your organization builds apps.
### Try It Yourself: Extending the Employee App
diff --git a/content/en/docs/refguide/general/studio-pro-overview/keyboard-shortcuts.md b/content/en/docs/refguide/general/studio-pro-overview/keyboard-shortcuts.md
index 26830a4c3a3..2b6ae960d24 100644
--- a/content/en/docs/refguide/general/studio-pro-overview/keyboard-shortcuts.md
+++ b/content/en/docs/refguide/general/studio-pro-overview/keyboard-shortcuts.md
@@ -206,9 +206,9 @@ The following shortcut keys are assigned to menu actions that can be used in all
| Ctrl + Shift + W | Command + Shift + W | Closes all document tabs. |
| Delete | Delete | Deletes the selected element. |
-## Maia Shortcut Keys {#maia-chat-shortcuts}
+## Maia Chat Shortcut Keys {#maia-chat-shortcuts}
-You can use the following shortcut keys in [Maia](/refguide/maia-make/) in the **Chat** tab. In Studio Pro 11.7 and below, these shortcuts work in [Maia Chat](/refguide/maia-chat/), including on the feedback page:
+You can use the following shortcut keys in [Maia Chat](/refguide/maia-chat/), including on the feedback page:
| Windows | Mac | Description |
| --- | --- | --- |
diff --git a/content/en/docs/refguide/mendix-ai-assistance/_index.md b/content/en/docs/refguide/mendix-ai-assistance/_index.md
index 1870da51fbe..7fb3a0de091 100644
--- a/content/en/docs/refguide/mendix-ai-assistance/_index.md
+++ b/content/en/docs/refguide/mendix-ai-assistance/_index.md
@@ -2,25 +2,16 @@
title: "Mendix AI Assistance (Maia)"
url: /refguide/mendix-ai-assistance/
weight: 17
-description: "Describes Mendix AI Assistance (Maia), the agentic development capability that supports you across the application lifecycle in Mendix Portal, Studio Pro, and Mendix Cloud."
+description: "Describes Mendix AI Assistance (Maia) in Studio Pro."
aliases:
- /refguide/mx-assist-studio-pro/
---
## Introduction
-Mendix AI Assistance (Maia) is the agentic development capability of the Mendix Platform. With agentic development, you give an agent a development goal, and the agent carries out the work by determining which documents to create or change, using tools, and asking clarifying questions when it needs more information. You direct the work and review the result. Maia supports you in this way across the full application lifecycle, from learning and planning, through modeling and building, to quality improvement, operation, and the ongoing evolution of your app.
+Mendix AI Assistance (Maia) refers to Mendix Platform capabilities that leverage [artificial intelligence (AI)](https://www.mendix.com/glossary/artificial-intelligence-ai/) and [machine learning (ML)](https://www.mendix.com/glossary/machine-learning/) to assist developers in application development. Maia is designed to help development teams in modeling and delivering Mendix applications faster, more consistently, and with higher quality.
-Maia is not a single feature. It is a set of capabilities that share one foundation: the Mendix app model. A Mendix app consists of model documents, such as domain models, pages, microflows, and workflows. Maia reads and changes these same documents. For example, when Maia generates a microflow, the result is a regular microflow that you can open, inspect, and change in Studio Pro, just like a microflow that you model yourself.
-
-This foundation has the following practical results for you as a developer:
-
-* Maia works with your app as context when generating content. For example, when Maia generates a page, it knows the domain model of the module you are working in. You can also add specific documents to the conversation to give Maia more context.
-* Maia creates and updates documents directly in the regular Studio Pro editors. Studio Pro checks these documents for consistency errors just as it does with documents you create yourself.
-* You stay in control of the development process. You decide what Maia builds, review the changes, and undo them if needed. When you are satisfied with the result, you commit the changes to version control.
-* You can extend Maia with your own conventions, connect external tools, use your own AI provider, or use your own agent with Studio Pro. Agent instructions and agent skills follow industry standards, so they work with any agentic tool.
-
-Maia works with professional developers; it does not replace them. Maia takes on tasks such as creating a first version of a document, applying conventions, explaining existing logic, and detecting anti-patterns. You keep ownership of the requirements, the architecture, and the quality of your app. For more information on this approach, see [Agentic and Model-Driven Development](/refguide/agentic-development/).
+Mendix developers can use Maia to get guidance by asking questions, get recommendation and assistance for certain development tasks, and even generate part of their app.
Maia does not use any project, customer, company, or user-entered data for model training. Maia operates on pre-trained, off-the-shelf large language models (LLMs). For more information on Mendix data storage policies and practices for Maia, see [Maia Privacy Policy](https://www.mendix.com/legal/privacy/maia/).
@@ -34,144 +25,80 @@ For information on what third-party services Maia uses and what data are sent to
For more information on how to ensure optimal performance of Maia, see the [Best Practice for Maia Performance](#maia-performance-best-practice) section below.
-## Maia Across the Application Lifecycle {#lifecycle}
-
-Maia is available at each stage of the application lifecycle. In Studio Pro, Maia Make is the single chat interface for all build stages: in one conversation, you can create and change any part of your model, such as data, logic, UI, workflows, and translations, and ask for guidance. The table below gives an overview. For a detailed description of each stage, including example prompts, see [Maia Across the Development Lifecycle](/refguide/maia-development-lifecycle/).
-
-| Lifecycle Stage | How Maia Helps | Capabilities |
-| --- | --- | --- |
-| Discover and learn | Explains Mendix concepts and answers development questions. |
- [Maia Learn](/refguide/maia-learn/)
- [Maia Make](/refguide/maia-make/)
|
-| Plan and design | Turns an app idea into a project scope, epics, and user stories. | - [Maia Plan](/developerportal/maia-plan/)
- [Create Story with Maia and Refine Story with Maia](/portal/maia/#maia-capabilities-in-mendix-portal)
|
-| Generate the app | Generates a first version of an app from a description, an image, a PDF, or a plan. | - [Start with Maia](/refguide/start-with-maia/)
- [Maia Make](/refguide/maia-make/)
|
-| Model data | Generates and changes domain models, view entities, enumerations, and OQL queries. | - [Maia Make](/refguide/maia-make/)
- [Domain Models in Maia Make](/refguide/maia-for-domain-model/)
- [OQL in Maia Make](/refguide/maia-for-oql/)
|
-| Create logic | Generates and changes microflows, recommends the next activity in a flow, and builds validation logic. | - [Maia Make](/refguide/maia-make/)
- [Logic Recommender](/refguide/logic-recommender/)
- [Validation Assist](/refguide/validation-assist/)
|
-| Create UI | Generates and changes pages, navigation, menus, and theme styling. Recommends widgets in the page editor. | - [Maia Make](/refguide/maia-make/)
- [Pages in Maia Make](/refguide/maia-for-pages/)
- [UI Recommender](/refguide/ui-recommender/)
|
-| Create workflows | Generates workflows from a process description or a BPMN image. Recommends the next workflow activity. | - [Maia Make](/refguide/maia-make/)
- [Workflows in Maia Make](/refguide/maia-for-workflows/)
- [Workflow Recommender](/refguide/workflow-recommender/)
|
-| Integrate | Creates JSON structures and data transformers, reads public APIs, and uses tools from external MCP servers. | - [Maia Make](/refguide/maia-make/)
- [Maia Web Fetch](/refguide/maia-web-fetch/)
- [Maia MCP Client](/refguide/maia-mcp/)
|
-| Understand and get guidance | Explains existing documents and consistency errors, and applies your team conventions. | - [Maia Make](/refguide/maia-make/)
- [Maia Explain](/refguide/maia-explain/)
- [Agent Instructions](/refguide/maia-agent-instructions/)
- [Agent Skills](/refguide/maia-agent-skills/)
|
-| Improve quality | Detects anti-patterns, explains their impact, and fixes some of them automatically. Explains and solves consistency errors. | - [Maia Make](/refguide/maia-make/)
- [Best Practice Recommender](/refguide/best-practice-recommender/) |
-| Localize | Creates and updates translations of the texts in your app (Studio Pro 11.15 and above). |
- [Maia Make](/refguide/maia-make/)
- [Translation Generator](/refguide/translation-generator/)
|
-| Work with external AI agents | Lets external AI agents use Maia capabilities, and lets Maia use your own AI provider. | - [Studio Pro MCP Server](/refguide/studio-pro-mcp-server/)
- [Maia Plan as MCP Server](/developerportal/maia-plan-mcp/)
- [Custom AI provider](/refguide/maia-make/#custom-provider) (beta)
|
-| Operate and evolve | Summarizes application logs, organizes end-user feedback, and changes existing documents for new requirements. | - [AI Log Summary](/developerportal/maia-operate/ai-log-summary/) (beta)
- [Maia for Feedback](/portal/maia/#maia-capabilities-in-mendix-portal)
- [Maia Make](/refguide/maia-make/)
|
-
-## Ways to Work with Maia {#ways-to-work}
-
-You can work with Maia in different ways. Choose the way that fits your task:
-
-* Agentic development in Studio Pro – Use [Maia Make](/refguide/maia-make/) as your single chat interface for building with Maia. Describe the goal, and Maia creates or changes the necessary documents, whether they are data, logic, UI, workflows, or translations. You can also ask questions and get explanations in the same conversation. Maia can be accessed in the **Maia** pane.
-* In-editor recommendations in Studio Pro – Use the [in-editor recommenders](/refguide/preferences-dialog/#in-editor-recommender) while you model. They suggest the next activity, widget, or fix in the editor you have open. Most recommenders work offline and do not send data to third-party services.
-* Planning and collaboration in Mendix Portal – Use [Maia in Mendix Portal](/portal/maia/) to plan an app, write and refine user stories, and organize feedback.
-* Operations in Mendix Cloud – Use [Maia Operate](/developerportal/deploy/maia-operate/) to get AI-generated insights into apps that run on Mendix Cloud.
-* Your own agent or AI provider – Use the [Studio Pro MCP Server](/refguide/studio-pro-mcp-server/) to work with Maia capabilities from your own agent, or [configure a custom AI provider](/refguide/maia-make/#custom-provider) for Maia. For an overview of these options, see [Using Maia with External AI Agents](/refguide/maia-external-agents/).
-
-## Maia Capabilities in Mendix Studio Pro {#maia-capabilities-in-mendix-studio-pro}
-
-Mendix AI Assistance (Maia) in Studio Pro has the following capabilities.
-
-### Starting Points
-
-* [Start with Maia](/refguide/start-with-maia/) – Start with Maia helps you start the app development process in Studio Pro. Provide a text description and an optional image or PDF, and Maia generates an app that includes a domain model, data management overview pages, test data, and a tailored homepage.
+## Maia Usage Limits {#maia-usage}
-### Agentic Development with Maia Make
+To ensure a reliable experience with Maia, Mendix provides two ways to manage your usage: purchasing Maia Units and configuring a custom AI provider of your choice. Every company receives 2400 free units per month and can purchase more as needed.
-* [Maia Make](/refguide/maia-make/)– Maia Make is a unified conversational interface in Studio Pro that groups all agentic development capabilities into a single chat experience. Start a conversation, describe what you need, and Maia creates or changes the necessary parts of your model. In the same conversation, you can ask questions and ask Maia to explain documents, such as your app logic and pages.
+When your free Maia Units allocation or purchased Maia Units have been consumed, you receive a notification in Studio Pro indicating that you need to take action before you can use Maia Make again. Your allocation resets at the start of each month. To increase your capacity, you can purchase additional Maia Units. For more information on purchasing Maia Units, see [Increasing Your Maia Usage Capacity](/control-center/maia-resources/#increase-maia-units).
-{{% alert type="info" %}}
-Maia Make was introduced as a unified conversational interface in Studio Pro 11.8, replacing the earlier document-specific tools: Maia for Domain Model, Maia for Pages, Maia for OQL, and Maia for Workflows.
+If you need uninterrupted access to Maia capabilities, you can [configure a custom AI provider](/refguide/maia-make/#custom-provider) to use your own LLM provider.
-Studio Pro 11.8 introduced support for domain models and pages in Maia Make. Studio Pro 11.9 added support for OQL and workflows.
-{{% /alert %}}
+Alternatively, you can use the Studio Pro MCP Server's bring your own agent (BYO Agent) capabilities, which allows you to use Maia's capabilities directly from external clients, including AI coding assistants, agents, and other MCP-based LLM tools. For more information on the Studio Pro MCP Server, see [Studio Pro MCP Server](/refguide/studio-pro-mcp-server/).
-The following pages explain how Maia Make works with each document type and describe how to use the earlier tools in older Studio Pro versions:
+## Network Configuration Requirements {#maia-network-requirement}
-* **Domain models** – Maia generates new [domain models](/refguide/domain-model/), and explains and suggests improvements for existing ones. For more information, see [Domain Models in Maia Make](/refguide/maia-for-domain-model/).
+To ensure the smooth operation of Mendix AI Assistance (Maia), the following network requirements must be met:
-{{% alert type="info" %}}
-For Private Mendix Platform, this feature is supported for version 11.6 and above.
-{{% /alert %}}
+* Ensure access to hostnames within the `maia.mendix.com` and `mxassist.rnd.mendix.com` subdomains
+* Allow secure network traffic through port 443 (HTTPS) to enable uninterrupted operation of Maia
-* **Pages** – Maia generates a [page](/refguide/page/) and adds and configures widgets based on text input and an optional image. You can continue in the same conversation to ask Maia for further improvements and explanations. For more information, see [Pages in Maia Make](/refguide/maia-for-pages/).
+## Maia Capabilities in Mendix Studio Pro
-{{% alert type="info" %}}
-For Private Mendix Platform, this feature is supported for version 11.6 and above.
-{{% /alert %}}
+Mendix AI Assistance (Maia) in Studio Pro has the following capabilities:
-* **OQL** – Maia generates and manages [OQL (Object Query Language)](/refguide/oql/) queries. For more information, see [OQL in Maia Make](/refguide/maia-for-oql/).
-* **Workflows** – Maia generates a [workflow](/refguide/workflows/) from a use case in text or an image. For more information, see [Workflows in Maia Make](/refguide/maia-for-workflows/).
+Starting point for app creation:
-For all document types that Maia Make supports, see the [Supported Document Types](/refguide/maia-make/#supported-document-types) section of *Maia Make Capabilities*.
+* **Start with Maia** - a starting point in Studio Pro that helps you to start the app development process. Based on a required text description and an optional image or PDF, it generates an app that includes a domain model, data management overview pages, test data, and a tailored homepage. For more information, see [Start with Maia](/refguide/start-with-maia/).
+* **Maia Make** - a unified conversational interface in Studio Pro that groups all AI-assisted development capabilities into a single chat experience. With this interface, everything happens in one place. Start a conversation, describe what you need, and Maia generates the necessary app artifacts, such as a new domain model, pages, and microflows. You can also ask it to explain documents for you, including your app logic and pages.
-### Guidance and Learning
+ This unified conversational interface was released in Studio Pro 11.8. For more information, see [Maia Make](/refguide/maia-make/).
-In Studio Pro 11.8 and above, [Maia Make](/refguide/maia-make/) replaces Maia Chat, the earlier chat interface in Studio Pro. You can use Maia's chat interface to ask questions and request explanations.
+Guidance:
-* **[Chat with Maia](/refguide/maia-chat/)** – Ask questions about app development in Mendix using Maia's chat feature, including how to apply concepts, best practices, and development patterns.
-* [Maia Learn](/refguide/maia-learn/) – Learn Mendix core concepts quickly to get started with Studio Pro.
-* [Maia Explain](/refguide/maia-explain/) – Maia Explain helps you understand existing documents, such as microflows and pages. It explains the general purpose of the document and highlights specific technical details.
+* **Maia Chat** – a built-in chat interface powered by Generative AI in Studio Pro. It answers questions about app development in Mendix, including how to apply concepts, best practices, and development patterns. For more information, see [Maia Chat](/refguide/maia-chat/).
+* **Maia Learn** – helps you to quickly learn Mendix core concepts and get started with Studio Pro. For more information, see [Maia Learn](/refguide/maia-learn/).
+* **Maia Explain** – helps you easily understand a microflow or a nanoflow. It explains the general purpose of the logic and highlights specific technical details to help you understand the logic further. For more information, see [Maia Explain](/refguide/maia-explain/).
+* **Maia Agent Skills** – lets you define modular, reusable instructions that extend Maia with domain-specific knowledge. Maia applies them automatically whenever relevant, eliminating the need to repeat the same context across conversations. For more information, see [Maia Agent Skills (SKILLS.md)](/refguide/maia-agent-skills/).
+* **Maia Agent Instructions** – allows you to define project- or module-level instructions (AGENTS.md) that steer agent behavior. You can use them to set common context for your prompts, such as company conventions or environment restrictions. For more information, see [Maia Agent Instructions (AGENTS.md)](/refguide/maia-agent-instructions/).
+* **Maia Plan Mode** – allows you to create detailed plans of implementation for whole apps or large application features. For more information, see [Maia Plan Mode](/refguide/maia-plan-mode/).
-### Context and Customization
+Recommenders:
-* [Agent Instructions (AGENTS.md)](/refguide/maia-agent-instructions/) – Agent instructions allows you to define project- or module-level instructions (`AGENTS.md`) that steer agent behavior. You can use them to set common context for your prompts, such as company conventions or environment restrictions.
-* [Agent Skills (SKILLS.md)](/refguide/maia-agent-skills/) – Agent skills lets you define modular, reusable instructions that extend Maia with domain-specific knowledge. Maia applies them automatically whenever relevant, which removes the need to repeat the same context across conversations.
-* [Maia MCP Client](/refguide/maia-mcp/) – Maia MCP Client connects Maia to external MCP servers, giving it access to third-party tools during chat.
-* [Maia Web Fetch](/refguide/maia-web-fetch/) – Maia Web Fetch lets Maia retrieve and read content from public websites and APIs, after you approve the request.
+* **Best Practice Recommender** – helps you inspect your app against Mendix development best practice detecting and pinpointing development anti-patterns and, in some cases, automatically fixing them. For more information, see [Best Practice Recommender](/refguide/best-practice-recommender/).
+* **Logic Recommender** – helps you model and configure microflows, nanoflows, and rules in Mendix Studio Pro. It gives you contextualized recommendations on the next best activity based on the activities and parameters that are already configured in your application. For more information, see [Logic Recommender](/refguide/logic-recommender/).
+* **UI Recommender** – helps you easily add new widgets to a page in Mendix Studio Pro without losing the context of what you are currently working on. For more information, see [UI Recommender](/refguide/ui-recommender/).
+* **Workflow Recommender** – helps you model and configure workflows in Mendix Studio Pro. It gives you contextualized recommendations on the next best activity in your workflow based on context-related information. For more information, see [Workflow Recommender](/refguide/workflow-recommender/).
-### Recommenders
+Generators:
-* [Best Practice Recommender](/refguide/best-practice-recommender/) – Best Practice Recommender helps you inspect your app against Mendix development best practices. It detects and pinpoints development anti-patterns and, in some cases, fixes them automatically.
-* [Logic Recommender](/refguide/logic-recommender/) – Logic Recommender helps you model and configure microflows, nanoflows, and rules in Mendix Studio Pro. It gives you contextualized recommendations on the next best activity based on the activities and parameters that are already configured in your application.
-* [UI Recommender](/refguide/ui-recommender/) – UI Recommender helps you add new widgets to a page in Mendix Studio Pro without losing the context of what you are currently working on.
-* [Workflow Recommender](/refguide/workflow-recommender/) – Workflow Recommender helps you model and configure workflows in Mendix Studio Pro. It gives you contextualized recommendations on the next best activity in your workflow based on context-related information.
-* [Validation Assist](/refguide/validation-assist/) – Validation Assist helps you build validation microflows in a more automated way using pre-built expressions.
-### Localization
+* **Maia for Domain Model** – helps you generate new [domain models](/refguide/domain-model/), and explain and provide suggestions for existing domain models. For more information, see [Maia for Domain Model](/refguide/maia-for-domain-model/).
-* [Translation Generator](/refguide/translation-generator/) – The Translation Generator helps with [batch translate](/refguide/translation-generator/#batch-translate) and [translating system texts](/refguide/translation-generator/#translate-system-text) in the web-based system texts editor.
+ For Private Mendix Platform, this feature is supported for version 11.6 and newer.
+
+* **Maia for Pages** – helps you generate a [page](/refguide/page/). It helps you add and configure widgets based on a text input and an optional image. After a page is generated, you can continue in the same session to ask Maia for further improvements and explanations. For more information, see [Maia for Pages](/refguide/maia-for-pages/).
-### External AI Agents and AI Providers
+ For Private Mendix Platform, this feature is supported for version 11.6 and newer.
-* [Studio Pro MCP Server](/refguide/studio-pro-mcp-server/) – The Studio Pro MCP Server exposes Maia capabilities to external AI agents and AI coding assistants through the Model Context Protocol (MCP). This is also known as bring your own agent (BYO Agent).
-* Custom AI provider – A custom AI provider lets Maia use your own LLM provider instead of the Mendix platform AI service. This is also known as bring your own LLM (BYO LLM). This feature is available in Studio Pro 11.12 and above as a beta feature. For more information, see the [Configuring a Custom AI Provider](/refguide/maia-make/#custom-provider) section in *Maia Make Capabilities*.
-
-For an overview of how these options work together, see [Using Maia with External AI Agents](/refguide/maia-external-agents/).
+* **Maia for OQL** – helps you generate and manage OQL (Object Query Language) queries through an intuitive interface. It is designed to simplify query creation and reduce manual effort. For more information, see [Maia for OQL](/refguide/maia-for-oql/).
+* **Maia for Workflows** – helps you generate a [Workflow](/refguide/workflows/). By providing a use case via text input or an image, Maia can help you start creating your workflows. For more information, see [Maia for Workflows](/refguide/maia-for-workflows/).
+* **Translation Generator** – helps you with [batch translate](/refguide/translation-generator/#batch-translate) and [translating system texts](/refguide/translation-generator/#translate-system-text) in the web-based system texts editor. For more information, see [Translation Generator](/refguide/translation-generator/).
+* **Validation Assist** – helps you build validation microflows in a more automated way using pre-built expressions. For more information, see [Validation Assist](/refguide/validation-assist/).
## Maia in Mendix Portal
-[Maia in Mendix Portal](/portal/maia/) supports the planning and collaboration stages of the lifecycle. You can use Maia Plan to turn an app idea into a project scope and solution, create and refine user stories, organize end-user feedback, and ask questions in Maia Chat.
-
-## Maia in Mendix Cloud
-
-[Maia Operate](/developerportal/deploy/maia-operate/) supports the operation stage of the lifecycle for apps that run on Mendix Cloud. For example, AI Log Summary, which is in Public Beta, gives you an AI-generated overview of the log activity of an environment.
+Various Maia features are available in Mendix Portal. For more information, refer to [Maia in Mendix Portal](/portal/maia/).
## Maia in Private Mendix Platform
Various Maia features are available in Private Mendix Platform. For more information, refer to [Maia in Private Mendix Platform](/private-mendix-platform/maia/).
-## Maia Usage Limits {#maia-usage}
-
-To ensure a reliable experience with Maia, Mendix provides two ways to manage your usage: purchasing Maia Units and configuring a custom AI provider of your choice. Every company receives 2400 free units per month and can purchase more as needed.
-
-When your free Maia Units allocation or purchased Maia Units have been consumed, you receive a notification in Studio Pro indicating that you need to take action before you can use Maia Make again. Your allocation resets at the start of each month. To increase your capacity, you can purchase additional Maia Units. For more information on purchasing Maia Units, see [Increasing Your Maia Usage Capacity](/control-center/maia-resources/#increase-maia-units).
-
-If you need uninterrupted access to Maia capabilities, you can [configure a custom AI provider](/refguide/maia-make/#custom-provider) to use your own LLM provider.
-
-Alternatively, you can use the Studio Pro MCP Server's bring your own agent (BYO Agent) capabilities, which allows you to use Maia's capabilities directly from external clients, including AI coding assistants, agents, and other MCP-based LLM tools. For more information on the Studio Pro MCP Server, see [Studio Pro MCP Server](/refguide/studio-pro-mcp-server/).
-
-## Network Configuration Requirements {#maia-network-requirement}
-
-To ensure the smooth operation of Mendix AI Assistance (Maia), the following network requirements must be met:
-
-* Ensure access to hostnames within the `maia.mendix.com` and `mxassist.rnd.mendix.com` subdomains
-* Allow secure network traffic through port 443 (HTTPS) to enable uninterrupted operation of Maia
-
## Maia Third-Party Services {#maia-third-party-services}
{{% alert color="info" %}}
As of Studio Pro 11.12, Maia Make uses Claude Sonnet 4.6.
{{% /alert %}}
-[Maia Make](/refguide/maia-make/), introduced in Studio Pro 11.8, uses Claude Sonnet 4.5. Any Maia Make capability in Studio Pro 11.8 and above uses this model to generate Mendix models.
-
-If you [configure a custom AI provider](/refguide/maia-make/#custom-provider), Maia Make sends requests to the provider that you configure instead.
+[Maia Make](/refguide/maia-make/) introduced in Studio Pro 11.8 uses Claude Sonnet 4.5. Any Maia Make capability in Studio Pro 11.8 and above uses this model to generate Mendix models.
The table below presents all the third-party services each Maia capability uses for Studio Pro versions below 11.8, and what data are sent to the third-party services.
@@ -185,12 +112,12 @@ The table below presents all the third-party services each Maia capability uses
| Logic Recommender | No third-party services used | N/A |
| UI Recommender | No third-party services used | N/A |
| Workflow Recommender | No third-party services used | N/A |
-| Maia for Domain Models | [Claude in Amazon Bedrock](https://aws.amazon.com/bedrock/claude/) | Project context to fulfill user prompt request |
+| Maia for Domain Model | [Claude in Amazon Bedrock](https://aws.amazon.com/bedrock/claude/) | Project context to fulfill user prompt request |
| Maia for Pages | [Claude in Amazon Bedrock](https://aws.amazon.com/bedrock/claude/) | Project context to fulfill user prompt request |
| Maia for OQL | [Claude in Amazon Bedrock](https://aws.amazon.com/bedrock/claude/) | Project context to fulfill user prompt request |
| Maia for Workflows | [Claude in Amazon Bedrock](https://aws.amazon.com/bedrock/claude/) | Project context to fulfill user prompt request |
| Translation Generator | [Amazon Translate](https://aws.amazon.com/translate/) | All translatable texts in the application, for example, labels, button names, and menu items |
-| Validation Assist | No third-party services used | N/A |
+| Validation Assist | No third-party services used | NA |
| Maia Rewrite | [Claude in Amazon Bedrock](https://aws.amazon.com/bedrock/claude/) | The draft question description from users |
| Maia Summarize | [Claude in Amazon Bedrock](https://aws.amazon.com/bedrock/claude/) | [Community](https://community.mendix.com/p/community) threads |
| Maia Create User Story | [Claude in Amazon Bedrock](https://aws.amazon.com/bedrock/claude/) | User prompts |
@@ -198,13 +125,3 @@ The table below presents all the third-party services each Maia capability uses
## Best Practice for Maia Performance {#maia-performance-best-practice}
For optimal performance, Maia works best when handling focused, well-scoped requests. When working on complex or lengthy content generation tasks, you will get faster and more reliable results by breaking them into smaller, manageable steps. This approach not only reduces the risk of network issues, but often leads to higher-quality outputs that better meet your specific needs.
-
-For more working practices, such as how to give Maia context and how to review its changes, see the [Working Practices for Agentic Development](/refguide/agentic-development/#working-practices) section in *Agentic and Model-Driven Development*.
-
-## Read More
-
-* [Agentic and Model-Driven Development](/refguide/agentic-development/)
-* [Maia Across the Development Lifecycle](/refguide/maia-development-lifecycle/)
-* [Using Maia with External AI Agents](/refguide/maia-external-agents/)
-* [Maia Make Capabilities](/refguide/maia-make/)
-* [Enrich Your Mendix App with Agentic Capabilities](/agents/)
\ No newline at end of file
diff --git a/content/en/docs/refguide/mendix-ai-assistance/maia-development-lifecycle.md b/content/en/docs/refguide/mendix-ai-assistance/maia-development-lifecycle.md
deleted file mode 100644
index df8dfe01797..00000000000
--- a/content/en/docs/refguide/mendix-ai-assistance/maia-development-lifecycle.md
+++ /dev/null
@@ -1,197 +0,0 @@
----
-title: "Maia Across the Development Lifecycle"
-linktitle: "Maia Across the Lifecycle"
-url: /refguide/maia-development-lifecycle/
-weight: 1
-description: "Describes how Maia supports you at each stage of the application lifecycle, from learning and planning to building, quality improvement, operation, and evolution."
----
-
-## Introduction
-
-Mendix AI Assistance (Maia) supports you at each stage of the application lifecycle. In the build stages, Maia works as an agent. You describe the goal, and Maia creates or changes the necessary documents. In other stages, Maia gives guidance, recommendations, and insights.
-
-The stages do not need to be followed in a specific order. You will often move between them as you develop an app, such as when adding a feature to an existing app. Maia supports you through each stage, including when you revisit earlier work.
-
-This document describes each stage of the application lifecycle. For the principles behind this approach, see [Agentic and Model-Driven Development](/refguide/agentic-development/).
-
-## One Conversation for the Whole App Model {#one-conversation}
-
-In Studio Pro, [Maia Make](/refguide/maia-make/) provides a single chat interface for agentic development. You can use the same conversation to create and change any part of your app model, such as the domain model, logic, pages, workflows, and translations. You can also ask to get guidance and explanations.
-
-In Studio Pro 11.8 and above, the earlier document-specific tools, such as Maia for Pages and Maia for Workflows, are consolidated into [Maia Make](/refguide/maia-make/). This means you can use Maia Make to work with any supported part of your app model, without switching between tools. Individual documents such as [Pages in Maia Make](/refguide/maia-for-pages/) and [Workflows in Maia Make](/refguide/maia-for-workflows/) describe what Maia Make can do for a specific document type. For a full list of supported document types and the Studio Pro version that supports them, see the [Supported Document Types](/refguide/maia-make/#supported-document-types) section of *Maia Make Capabilities*.
-
-Next to the chat, the [in-editor recommenders](/refguide/preferences-dialog/#in-editor-recommender) and [Best Practice Recommender](/refguide/best-practice-recommender/) provide guidance as you model your app.
-
-{{% alert type="info" %}}
-In Studio Pro 11.7 and below, Maia Make capabilities are available through separate tools. See the relevant [Make Make Capabilities](/refguide/maia-make/#maia-make-capabilities-overview) documentation for information about accessing and using each tool.
-{{% /alert %}}
-
-## Discover and Learn {#discover-and-learn}
-
-When you start with Mendix, or with a new part of the platform, you need to understand the concepts and how to apply them.
-
-Maia helps in the following ways:
-
-* [Maia Learn](/refguide/maia-learn/) – Maia Learn guides you through the Mendix core concepts, such as domain models, pages, logic, security, and integrations, directly in Studio Pro.
-* [Maia Make](/refguide/maia-make/) – Maia Make answers questions about all aspects of Mendix development in the same chat in which you build, so you can move from a question to a change in your app in one conversation. Maia uses sources such as [Mendix Docs](https://docs.mendix.com/) and the [Mendix Community](https://community.mendix.com/link/home). In Studio Pro 11.8 and above, Maia Make replaces [Maia Chat](/refguide/maia-chat/), the earlier chat interface in Studio Pro. Maia Chat is still available in Studio Pro 11.7 and below and Mendix Portal.
-
-Below are example prompts you can use:
-
-* What is the difference between a microflow and a nanoflow?
-* How do I set up entity access for a role that can only see its own records?
-
-## Plan and Design {#plan-and-design}
-
-Before you build, you define what the app must do, for whom, and how you measure success.
-
-Maia helps in the following ways:
-
-* [Maia Plan](/developerportal/maia-plan/) – Maia Plan turns your project context, such as goals, target users, requirements, and attached documents, into a project scope. After you approve the scope, Maia generates a solution with epics and user stories. It can also recommend Marketplace components for specific stories.
-* **Create and Refine a Story with Maia** – Maia can help write new user stories and improve existing ones on the **Board** and **Planning** pages in Mendix Portal. For more information, see [Maia in Mendix Portal](/portal/maia/).
-
-You can use the stories from the plan as input when you build with Maia Make, which supports story-based development. Clear user stories with acceptance criteria give Maia better context.
-
-## Generate the App {#generate-the-app}
-
-When the scope is clear, use Maia to generate a first version of the app. This gives you a working starting point instead of an empty model.
-
-You have the following options:
-
-* From Maia Plan – In Maia Plan, select **Open in Studio Pro** to continue to work on the new app in Studio Pro with Maia Make. For more information, see [Starting the Development](/developerportal/maia-plan/start-development/).
-* [Start with Maia](/refguide/start-with-maia/) – In Studio Pro, select **Start with Maia** as your starting point. Describe your app using a text description and an optional image or PDF. Maia uses this input to generate a domain model, data management overview pages, test data, and a homepage.
-* Maia Make – In an existing app, describe a new module or feature in the **Maia** pane. Maia then generates the necessary documents.
-
-Review the generated app in the same way as any other change. For more information, see the [Review Every Change](/refguide/agentic-development/#working-practices) section of *Agentic and Model-Driven Development*.
-
-## Model Data {#model-data}
-
-The domain model is the foundation of every Mendix app. The other documents, such as pages and microflows, build on it.
-
-Maia helps in the following ways:
-
-* Maia Make – Maia Make generates new domain models, adds entities, attributes, and associations, and explains or improves existing domain models. In Studio Pro 11.9 and above, it can also work with [view entities](/refguide/view-entities/), enumerations, and constants, and generate OQL queries from a description of the data that you need. For more information, see [Domain Models in Maia Make](/refguide/maia-for-domain-model/) and [OQL in Maia Make](/refguide/maia-for-oql/).
-
-Below are example prompts you can use:
-
-* The app will help field engineers register maintenance visits. Each visit belongs to one asset and can have several photos.
-* Add a status enumeration to the Order entity with the values Draft, Submitted, and Approved.
-* Show all active orders with customer names.
-
-## Create Logic {#create-logic}
-
-Logic defines how your app behaves. In Mendix, you model logic with microflows, nanoflows, rules, and Java or JavaScript actions.
-
-Maia helps in the following ways:
-
-* Maia Make – Maia Make generates and changes microflows from a description. In Studio Pro 11.10 and above, it can also generate JavaScript actions. For the current scope per document type, see the [Supported Document Types](/refguide/maia-make/#supported-document-types) section of *Maia Make Capabilities*.
-* [Logic Recommender](/refguide/logic-recommender/) – The Logic Recommender recommends the next best activity while you model a microflow, nanoflow, or rule, and prefills its parameters.
-* [Validation Assist](/refguide/validation-assist/) – Validation Assist helps you build validation microflows with pre-built expressions, for example, for a button with the **Save changes** on-click event.
-
-Below are example prompts you can use:
-
-* Create a microflow that retrieves all open orders older than 30 days, changes their status to Expired, and commits them.
-* Add a decision to this microflow that shows an error message when the order has no order lines.
-
-## Create UI {#create-ui}
-
-Pages, navigation, and styling define how end-users experience your app.
-
-Maia helps in the following ways:
-
-* Maia Make – Maia Make generates pages from a text description and an optional image, such as a wireframe or screenshot. Maia knows the domain model of the module that you work in, so it can connect widgets to your entities. It can also change existing pages. In Studio Pro 11.11 and above, it can work with navigation and menus. In Studio Pro 11.12 and above, it can change theme variables and create custom styling. For more information, see [Pages in Maia Make](/refguide/maia-for-pages/).
-* [UI Recommender](/refguide/ui-recommender/) – The UI Recommender recommends widgets while you work in the page editor.
-
-Below are example prompts you can use:
-
-* Generate a page based on this image, but change the header to Welcome.
-* Add a list of the open maintenance visits for the current engineer to this page.
-
-## Create Workflows {#create-workflows}
-
-Workflows model processes that involve people and several steps, such as approvals and onboarding.
-
-Maia helps in the following ways:
-
-* Maia Make – Maia Make generates a workflow from a description of a business process or from a BPMN image, and changes existing workflows. For more information, see [Workflows in Maia Make](/refguide/maia-for-workflows/).
-* [Workflow Recommender](/refguide/workflow-recommender/) – The Workflow Recommender recommends the next best activity while you model a workflow.
-
-Below is an example prompt you can use:
-
-* Generate a workflow based on this BPMN image, but make sure it waits before sending an email to the new employee.
-
-## Integrate {#integrate}
-
-Most apps exchange data with other systems.
-
-Maia helps in the following ways:
-
-* Maia Make – Maia Make creates [JSON structures](/refguide/json-structures/) (Studio Pro 11.13 and above) and [data transformers](/refguide/data-transformers/) (Studio Pro 11.12 and above).
-* [Maia Web Fetch](/refguide/maia-web-fetch/) – Maia Web Fetch reads public API documentation and endpoints, after you approve each request. Maia can use this information when it creates integration documents.
-* [Maia MCP Client](/refguide/maia-mcp/) – Maia MCP Client connects Maia to external MCP servers, such as design tools or source code platforms. Maia can then use the tools of these servers during the conversation.
-
-## Understand and Get Guidance {#understand-and-get-guidance}
-
-You often work on documents that someone else created, or that you created a long time ago. Before you change them, you need to understand them.
-
-Maia helps in the following ways:
-
-* Maia Make – Ask in the chat about any document, concept, or error. [Maia Explain](/refguide/maia-explain/) describes the purpose and the technical details of an existing document. You can also start it in the **App Explorer** by right-clicking a document and selecting **Maia Explain**.
-* Explain consistency errors – In Studio Pro 11.12.1 and above, right-click an item in the **Errors** pane to ask Maia to explain or solve it.
-* [Agent Instructions (AGENTS.md)](/refguide/maia-agent-instructions/) and [Agent Skills (SKILLS.md)](/refguide/maia-agent-skills/) – Give Maia your team conventions and domain knowledge so its guidance and output follow your standards.
-
-Below are example prompts you can use:
-
-* Can you explain the function and purpose of this document?
-* Could you identify any potential issues with this document and recommend solutions?
-
-## Improve Quality {#improve-quality}
-
-Quality includes correctness, performance, security, and maintainability.
-
-Maia helps in the following ways:
-
-* [Best Practice Recommender](/refguide/best-practice-recommender/) – Use the Best Practice Recommender to inspect your app model against Mendix best practices. It detects anti-patterns, explains their impact, and in some cases fixes them automatically.
-* Maia Make – Maia Make explains and solves consistency errors, suggests improvements to existing documents, and helps you refactor. In Studio Pro 11.9 and above, Maia can remove elements as part of a refactoring.
-
-Use these capabilities on all documents, including the documents that Maia generates.
-
-## Localize {#localize}
-
-If your app serves users in several countries, it needs translated texts.
-
-Maia helps in the following ways:
-
-* **Maia Make** – In Studio Pro 11.15 and above, ask Maia in the chat to create or update the translations of texts in your app, as part of the same conversation in which you build the feature.
-* [Translation Generator](/refguide/translation-generator/) – The Translation Generator translates the texts in your app that do not have a translation yet in one batch, and translates system texts.
-
-## Work with External AI Agents {#external-agents}
-
-Some teams use AI coding assistants or their own AI agents next to Studio Pro. Some organizations require a specific AI provider.
-
-Maia supports these scenarios in the following ways:
-
-* [Studio Pro MCP Server](/refguide/studio-pro-mcp-server/) – The Studio Pro MCP Server exposes Maia capabilities to external AI agents through the Model Context Protocol (MCP). Changes appear in Studio Pro in real time.
-* [Maia Plan as MCP Server](/developerportal/maia-plan-mcp/) – Maia Plan as MCP Server gives external AI agents read-only access to the scope and solution of a Maia Plan project.
-* **Custom AI provider** – The Custom AI provider feature lets Maia use your own LLM provider. This feature is available in Studio Pro 11.12 and above as a beta feature. For more information, see the [Configuring a Custom AI Provider](/refguide/maia-make/#custom-provider) section of *Maia Make Capabilities*.
-
-For an overview of how these options work together, see [Using Maia with External AI Agents](/refguide/maia-external-agents/).
-
-## Operate and Evolve {#operate-and-evolve}
-
-After you deploy your app, you monitor it, collect feedback, and plan the next iteration.
-
-Maia helps in the following ways:
-
-* [AI Log Summary](/developerportal/maia-operate/ai-log-summary/) – This feature is in Public Beta. For apps that run on Mendix Cloud, it gives an AI-generated overview of the log activity of an environment over the previous 24 hours. It groups errors by pattern and shows lifecycle events and security signals. It is not available in Mendix Cloud Africa (Cape Town).
-* Maia for Feedback – This feature organizes end-user feedback into groups. You can create stories from feedback with Maia. For more information, see [Feedback](/developerportal/app-insights/feedback/).
-* Maia Make – Maia Make changes existing documents for new requirements. Use Maia Explain first to understand the current behavior, then ask Maia to make the change.
-
-New stories from feedback bring you back to the [Plan and Design](#plan-and-design) stage. This closes the loop of the lifecycle.
-
-## Read More
-
-* [Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/)
-* [Agentic and Model-Driven Development](/refguide/agentic-development/)
-* [Maia Make Capabilities](/refguide/maia-make/)
-* [Maia in Mendix Portal](/portal/maia/)
-* [Maia Operate](/developerportal/deploy/maia-operate/)
diff --git a/content/en/docs/refguide/mendix-ai-assistance/maia-external-agents.md b/content/en/docs/refguide/mendix-ai-assistance/maia-external-agents.md
deleted file mode 100644
index ef9e0b7d9cb..00000000000
--- a/content/en/docs/refguide/mendix-ai-assistance/maia-external-agents.md
+++ /dev/null
@@ -1,95 +0,0 @@
----
-title: "Using Maia with External AI Agents"
-linktitle: "External AI Agents"
-url: /refguide/maia-external-agents/
-weight: 6
-description: "Describes how Maia works with external AI agents, AI coding assistants, MCP servers, and custom AI providers, and how to combine these options."
----
-
-## Introduction
-
-Many development teams use AI tools alongside Studio Pro, such as AI coding assistants, their own AI agents, or a company-approved AI provider. Maia is designed to work with these tools by using open standards, including the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction), the [AGENTS.md](https://agents.md) format, and the [Agent Skills](https://agentskills.io/) format.
-
-## Integration Options {#integration-options}
-
-The table below lists the integration options available. Each option connects Maia and external AI tools in a different direction:
-
-| Option | Direction | When to Use | Available From |
-| --- | --- | --- | --- |
-| [Maia MCP Client](/refguide/maia-mcp/) | Maia uses tools from external MCP servers. | When a conversation requires information or actions from other systems, such as design assets or a source code platform. | Studio Pro 11.8 |
-| [Studio Pro MCP Server](/refguide/studio-pro-mcp-server/) | External AI agents use Maia capabilities in Studio Pro. | When working with an AI agent or AI coding assistant to create and modify Mendix documents. This is also known as bring your own agent (BYO Agent). | Studio Pro 11.10 |
-| [Maia Plan as MCP Server](/developerportal/maia-plan-mcp/) | External AI agents read Maia Plan content. | When an external AI agent needs access to the scope, epics, and stories of a Maia Plan project. | Mendix Portal |
-| [Custom AI provider](/refguide/maia-make/#custom-provider) | Maia uses your LLM provider. | When an organization requires a specific LLM provider or uninterrupted access to Maia without Maia Units. This is also known as bring your own LLM (BYO LLM). | Studio Pro 11.12 (beta) |
-| [Agent Instructions](/refguide/maia-agent-instructions/) and [Agent Skills](/refguide/maia-agent-skills/) | Shared context for Maia and other agents. | When all agents need to follow the same conventions and use the same domain knowledge. Both follow industry standards, making them compatible with any agentic tool that supports these standards. | Studio Pro 11.11 (Agent SKills), Studio Pro 11.12 (Agent Instructions) |
-
-You can combine these options. For example, you can use a custom AI provider for Maia in Studio Pro, and connect Maia to an external MCP server at the same time.
-
-## Bring Your Own Agent {#byo-agent}
-
-The [Studio Pro MCP Server](/refguide/studio-pro-mcp-server/) lets external AI agents, such as an AI coding assistant, use the same capabilities as Maia in Studio Pro. These agent can generate and change Mendix documents, such as domain models, pages, and microflows, and Studio Pro shows the changes in real time.
-
-{{% alert type="info" %}}
-In Studio Pro 11.10, the MCP Server cannot generate pages. For more information, see the [Limitations](/refguide/studio-pro-mcp-server/#limitations) section of *Studio Pro MCP Server*.
-{{% /alert %}}
-
-This approach has the following benefits:
-
-* You can work from one tool. If you already use an AI agent for other parts of your work, such as code, documentation, or tickets, you can also use it for your Mendix app.
-* The agent uses Maia capabilities to change your app. It works with Mendix documents, such as domain models and microflows.
-* You review the changes in the Studio Pro editors and in the **Errors** pane, in the same way as changes from Maia in Studio Pro.
-* Agent instructions and agent skills follow the `AGENTS.md` and Agent Skills standards. They work with Maia and with other agentic tools, so your external agent can use the same conventions as Maia.
-
-The Studio Pro MCP Server runs locally on your workstation, so you do not need to be signed in to Studio Pro to use it. Mendix platform MCP servers, such as Maia Plan as MCP Server, require authentication with your Mendix account.
-
-When you use an external agent, the agent uses tokens from your own LLM provider account. Usage and billing are managed by your LLM provider, not by Mendix.
-
-To set up the Studio Pro MCP Server, see the [Enabling the MCP Server](/refguide/studio-pro-mcp-server/#enabling-the-mcp-server) section of *Studio Pro MCP Server*.
-
-## Bring Your Own LLM {#byo-llm}
-
-By default, Maia uses the Mendix platform AI service. This is the recommended option. It requires no configuration and includes Mendix platform optimizations.
-
-If you configure a custom AI provider, [Maia Make](/refguide/maia-make/) sends its requests to the provider you select, such as Amazon Bedrock or an OpenAI-compatible endpoint. Custom AI provider settings are per project and local to your workstation. They are not committed to version control. Some Mendix platform optimizations may not be available with a custom provider.
-
-To configure a custom AI provider, see the [Configuring a Custom AI Provider](/refguide/maia-make/#custom-provider) section of *Maia Make Capabilities*.
-
-## Extend Maia with External Tools {#extend-maia}
-
-The [Maia MCP Client](/refguide/maia-mcp/#) lets Maia call tools from remote MCP servers during a conversation. For example, Maia can look up design assets or interact with a source code platform. Studio Pro includes a preset connection to the Mendix Marketplace and a catalog of other preset servers.
-
-Tools from a new server are disabled by default, so you can choose which tools Maia has access to and enable only the ones you need.
-
-## Example: From Plan to Implementation with an External Agent {#example}
-
-The following example shows how you can combine the options.
-
-A team plans an app in Mendix Portal and uses an AI coding assistant to implement the stories in Studio Pro.
-
-1. Create a plan in [Maia Plan](/developerportal/maia-plan/). Review the scope, epics, and stories.
-2. In your AI coding assistant, configure the [Maia Plan MCP Server](/developerportal/maia-plan-mcp/#configure) with a personal access token that has the `mx:plan:v1:read` scope.
-3. Open the app in Studio Pro and [enable the Studio Pro MCP Server](/refguide/studio-pro-mcp-server/#enabling-the-mcp-server). Connect your AI coding assistant to it.
-4. Add an [AGENTS.md](/refguide/maia-agent-instructions/) file with your team conventions, such as naming rules and the modules that the agent must not change. Agent instructions guide the agent, but they do not enforce restrictions, so check the result in step 6.
-5. In your AI coding assistant, ask the agent to get one story from the plan and implement it in a specific module.
-6. Review the result in Studio Pro. Check the changed documents and the **Errors** pane, and run [Best Practice Recommender](/refguide/best-practice-recommender/).
-7. Test the functionality and commit the changes.
-
-Repeat steps 5 to 7 for each story. Implement one story at a time so each change stays small enough to review.
-
-## Security and Control {#security-and-control}
-
-Keep the following points in mind when you connect external AI tools:
-
-* Authentication – The Studio Pro MCP Server runs locally and does not require you to be signed in to Studio Pro. Mendix platform MCP servers require authentication with your Mendix account.
-* Credentials – Store personal access tokens and API keys securely, for example, in environment variables. Do not commit them to version control.
-* Tool access – Enable only the MCP tools Maia needs. Tools from new servers are disabled by default.
-* Web access – Maia asks for your approval before it fetches web content. For more information, see [Maia Web Fetch](/refguide/maia-web-fetch/).
-* Data – When you use an external agent or a custom AI provider, your prompts and project context go to that provider. Check that the provider meets the data requirements of your organization. For information on the services that Maia uses by default, see the [Maia Third-Party Services](/refguide/mendix-ai-assistance/#maia-third-party-services) section of *Mendix AI Assistance (Maia)*.
-* Review – Changes from an external agent are regular changes to your app. Review all changes before you commit them.
-
-## Read More
-
-* [Studio Pro MCP Server](/refguide/studio-pro-mcp-server/)
-* [Maia MCP Client](/refguide/maia-mcp/)
-* [Maia Plan as MCP Server](/developerportal/maia-plan-mcp/)
-* [Agentic and Model-Driven Development](/refguide/agentic-development/)
-* [Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/)
diff --git a/content/en/docs/refguide/mendix-ai-assistance/maia-learn.md b/content/en/docs/refguide/mendix-ai-assistance/maia-learn.md
index a45e78083d0..b789fb22858 100644
--- a/content/en/docs/refguide/mendix-ai-assistance/maia-learn.md
+++ b/content/en/docs/refguide/mendix-ai-assistance/maia-learn.md
@@ -29,8 +29,8 @@ Click **Mendix Core Concepts**, you can start your learning journey with Maia Le
You can also access additional materials on the topic, such as related documentation or a learning path.
-If you have any questions during the learning journey, you can click **Ask Maia** and ask your questions in [Maia's chat interface](/refguide/maia-chat/).
+If you have any questions during the learning journey, you can always click **Ask Maia** and ask your questions in [Maia Chat](/refguide/maia-chat/) for further assistance.
## Read More
-* [Chat with Maia](/refguide/maia-chat/)
+* [Maia Chat](/refguide/maia-chat/)
diff --git a/content/en/docs/refguide/mendix-ai-assistance/maia-make/_index.md b/content/en/docs/refguide/mendix-ai-assistance/maia-make/_index.md
index 32eae038fd1..2dd3689de0a 100644
--- a/content/en/docs/refguide/mendix-ai-assistance/maia-make/_index.md
+++ b/content/en/docs/refguide/mendix-ai-assistance/maia-make/_index.md
@@ -15,13 +15,11 @@ Maia Make capabilities are available in Studio Pro 11.8 and above.
To use Maia Make capabilities, you need an internet connection. You must be signed in to Studio Pro unless you have configured a bring your own agent (BYO Agent).
{{% /alert %}}
-Maia Make is a set of agentic development capabilities in Studio Pro that are available through a unified conversational interface. In one conversation, you can describe your requirements in natural language, and have Maia generate or modify any part of your app model, including domain models, pages, microflows, workflows, and translations. You can also ask Maia to explain existing documents, provide guidance, and integrate with external tools, such as Playwright and Figma, via MCP servers.
+Maia Make is a set of AI-assisted development capabilities in Studio Pro that are available through a unified conversational interface. Describe your requirements in natural language, and Maia generates development artifacts such as data structures, pages, and microflows.
-Maia Make also supports story-based development, allowing you to generate app artifacts based on existing user stories. As an agent that works directly with your app model, Maia determines which documents to create or change based on your goals, its built-in capabilities, and the MCP tools you enable. When necessary, it asks clarifying questions to gather more information.
+You can also ask Maia to provide explanations of your existing documents, such as microflows, workflows, and pages. Moreover, this interface allows you to integrate with external tools, such as Playwright and Figma, via MCP servers. It also supports story-based development by generating app artifacts based on existing user stories.
-Maia creates and modifies regular Mendix documents that you can review in the Studio Pro editors and undo as needed. That makes Maia Make useful throughout the application lifecycle, from generating a first version of an app to refactoring and extending an existing one. For more information, see [Maia Across the Development Lifecycle](/refguide/maia-development-lifecycle/).
-
-For guidance on writing effective prompts for Maia, refer to [Prompt Engineering](/agents/prompt-engineering/).
+For guidance on how to best prompt Maia, refer to [Prompt Engineering](/agents/prompt-engineering/).
## Maia Make Capabilities Overview
@@ -55,13 +53,14 @@ The following table lists Maia Make Standalone Capabilities and the Studio Pro v
| Capability | Description | Available in Maia Make from | Remarks |
| --- | --- | --- | --- |
-| [Chat](/refguide/maia-chat/) | Answers questions about all aspects of Mendix development in the same chat in which you build. | Studio Pro 11.8 | Replaces Maia Chat, the earlier chat interface in Studio Pro. |
+| [Maia Chat](/refguide/maia-chat/) | Answers questions about all aspects of Mendix development. | Studio Pro 11.8 | |
| [Maia Explain](/refguide/maia-explain/) | Explains the purpose and logic of existing documents. | Studio Pro 11.8 | Can be used directly in the chat interface, or in the App Explorer by right-clicking a document and clicking **Maia Explain**. |
| [Maia MCP Client](/refguide/maia-mcp/) | Connects Maia to external MCP servers, giving it access to third-party tools. | Studio Pro 11.8 | |
| [Studio Pro MCP Server](/refguide/studio-pro-mcp-server/) | Exposes Studio Pro as an MCP server for use by external AI tools. | Studio Pro 11.10 | |
| [Maia Web Fetch](/refguide/maia-web-fetch/) | Fetches and reads content from public websites and APIs. | Studio Pro 11.10 | |
| [Maia Agent Skills (SKILLS.md)](/refguide/maia-agent-skills/) | Extends Maia with reusable knowledge. | Studio Pro 11.11 | Maia can create and edit skills directly in chat, for both project-level and module-level skills, from Studio Pro 11.15. |
| [Maia Agent Instructions (AGENTS.md)](/refguide/maia-agent-instructions/) | Extends Maia with instructions to be followed with every prompt | Studio Pro 11.12 | |
+| [Maia Plan Mode](/refguide/maia-plan-mode/) | Allows Maia to maintain implementation plans. | Studio Pro 11.16 | |
### Maia Make General Capabilities
@@ -79,7 +78,6 @@ The following table lists the general capabilities of Maia Make and the Studio P
| Themes and styling | Allows Maia to modify theme variables, create custom styling, and manage design properties. | Studio Pro 11.12 | |
| Markdown attachment support | Allows you to provide Markdown documents as input to help Maia better understand your requirements. | Studio Pro 11.12 | |
| Explain and solve consistency errors | Allows you to use Maia to explain or solve problems by right-clicking the item in the **Errors** pane. | Studio Pro 11.12.1 | |
-| Translations | Allows Maia to create and update translations in your app. | Studio Pro 11.15 | |
## Using Maia Make Capabilities
@@ -119,9 +117,9 @@ This option ({{% icon name="plug" %}}) allows you to connect external [MCP](http
{{< figure src="/attachments/refguide/mendix-ai-assistance/maia-make/maia-make-capabilities/add.jpg" width="250px" alt="" >}}
-#### Add File to Maia Chat
+#### Add file to Maia Chat
-The **Add file to Maia Chat** option (@ icon) allows you to add certain logic or pages to Maia as context. You can also access this option by right-clicking the documents (microflows or pages) in the **App Explorer**, where it appears in the context menu.
+This option (@ icon) allows you to add certain logic or pages to Maia as context. You can also access this option by right-clicking the documents (microflows or pages) in the **App Explorer**, where it appears in the context menu.
{{< figure src="/attachments/refguide/mendix-ai-assistance/maia-make/maia-make-capabilities/add-files.jpg" width="250px" alt="" >}}
@@ -139,18 +137,6 @@ This feature is available for Studio Pro 11.12 and above.
When Maia needs more information, it asks clarifying questions through a dedicated UI to improve the quality of its response.
-## Reviewing and Controlling Maia Changes {#reviewing-changes}
-
-Maia changes regular documents in your app. You stay in control of these changes in the following ways:
-
-* Changed list – After each request, the [Changed List](#changed-list) shows the documents that Maia added or changed. Select an entry to open the document in its editor.
-* Consistency checks – Studio Pro checks the documents that Maia creates or changes for consistency errors. In Studio Pro 11.12.1 and above, you can right-click an item in the [Errors](/refguide/errors-pane/) pane to ask Maia to explain or solve it.
-* Undo – In Studio Pro 11.9 and above, you can undo Maia changes per document or for all documents.
-* Version control – Maia changes are part of your local changes, so you decide when to commit them. For more information, see [Version Control](/refguide/version-control/).
-* Settings – You can disable Maia Make capabilities in Studio Pro [Preferences](/refguide/preferences-dialog/#ai-tab) on the **AI** tab.
-
-For practices that help you review and control AI-generated changes, see the [Working Practices for Agentic Development](/refguide/agentic-development/#working-practices) section of *Agentic and Model-Driven Development*.
-
## Save a Maia Session {#save-maia-session}
A Maia session contains your conversation history and context, which can help analyze Maia's responses and behavior for troubleshooting or support purposes. To save a Maia session, go to **Help** > **Support Tools** > **Capture Maia Agent Session**.
@@ -259,6 +245,3 @@ You can provide a BPMN image representing employee onboarding alongside your tex
## Read More
* [Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/)
-* [Agentic and Model-Driven Development](/refguide/agentic-development/)
-* [Maia Across the Development Lifecycle](/refguide/maia-development-lifecycle/)
-* [Using Maia with External AI Agents](/refguide/maia-external-agents/)
diff --git a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-agent-instructions.md b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-agent-instructions.md
index 7cd270a90c7..78809b825e7 100644
--- a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-agent-instructions.md
+++ b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-agent-instructions.md
@@ -62,4 +62,4 @@ Project-level instructions are stored as `skillssource/AGENTS.md`, while module-
* [Agent Skills](/refguide/maia-agent-skills/)
* [Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/)
-* [Chat with Maia](/refguide/maia-chat/)
+* [Maia Chat](/refguide/maia-chat/)
diff --git a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-agent-skills.md b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-agent-skills.md
index e758c630eab..b47cb29b43d 100644
--- a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-agent-skills.md
+++ b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-agent-skills.md
@@ -153,6 +153,6 @@ To apply the updated skills immediately, click the **Sync** button in the **Skil
* [Maia Make Capabilities](/refguide/maia-make/)
* [Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/)
-* [Chat with Maia](/refguide/maia-chat/)
+* [Maia Chat](/refguide/maia-chat/)
* [Best Practices for Skill Creators](https://agentskills.io/skill-creation/best-practices) – guidance on writing effective skill content
* [Agent Skills Specification](https://agentskills.io/specification) – the full specification for the agent skills format
diff --git a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-chat.md b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-chat.md
index f4ca0e9614e..5706688e959 100644
--- a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-chat.md
+++ b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-chat.md
@@ -1,9 +1,9 @@
---
-title: "Chat with Maia"
+title: "Maia Chat"
linktitle: "Chat"
url: /refguide/maia-chat/
weight: 5
-description: "Describes how to ask questions about Mendix development in Maia Make, and how Maia Chat worked in earlier versions of Studio Pro."
+description: "Describes how to use Maia Chat, the built-in AI chat interface in Studio Pro."
aliases:
- /refguide/mendix-chat/
#If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the product. See Mapping to Products for more details.
@@ -12,14 +12,20 @@ aliases:
## Introduction
{{% alert color="info" %}}
-In Studio Pro 11.8 and above, [Maia Make](/refguide/maia-make/) replaces Maia Chat, the earlier chat interface in Studio Pro. Maia Chat is still available in Mendix Portal. For more information, refer to the [Maia Chat](/portal/maia/#maia-chat) section in *Maia in Mendix Portal*.
+Maia Chat is also available in the Mendix Portal. For more information, refer to the [Maia Chat](/portal/maia/#maia-chat) section in *Maia in Mendix Portal*.
+{{% /alert %}}
-To ask questions in Studio Pro, you need an internet connection and must be signed in to Studio Pro.
+{{% alert color="info" %}}
+To use Maia Chat, you need an internet connection and must be signed in to Studio Pro.
{{% /alert %}}
-In Studio Pro, you can ask Maia questions about Mendix development in the **Chat** tab of the **Maia** pane. You can ask about all aspects of Mendix, including how to apply concepts, best practices, governance tools, and development patterns. Because you ask questions in the same chat in which you build, you can move from a exploring an idea to a implementing a change in your app in a single conversation.
+{{% alert color="info" %}}
+Maia Chat does not use any project, customer, or company information. It only uses the data you enter in the chat to fulfill the request. Do not enter any personal or sensitive data.
+{{% /alert %}}
+
+Maia Chat is a built-in chat interface in the Mendix Platform powered by generative AI. You can ask questions about all aspects of Mendix, including how to apply concepts, best practices, governance tools, and development patterns. It is based on large language models (LLMs) using data from various resources.
-To answer questions about Mendix, Maia uses the following data sources:
+Maia Chat uses the following data sources:
* [Mendix Docs](/)
* [Mendix Community](https://community.mendix.com/)
@@ -29,23 +35,19 @@ To answer questions about Mendix, Maia uses the following data sources:
* [Mendix Evaluation Guide](https://www.mendix.com/evaluation-guide/)
* [Mendix Support Knowledge Base](https://support.mendix.com/hc/en-us/p/knowledge-base) (in Studio Pro 11.10 and above)
-## Asking Questions in Maia {#asking-questions}
+## Using Maia Chat
-In Studio Pro 11.8 and above, open the **Maia** pane and ask your question in the **Chat** tab. There is no separate interface for questions. For more information, see [Maia Make Capabilities](/refguide/maia-make/).
+You can start using Maia Chat by clicking one of the demo questions. Alternatively, you can ask your own question, and press Enter or click **Ask** to send the question. For information on the supported shortcut keys in Maia Chat, see the [Maia Chat Shortcut Keys](/refguide/keyboard-shortcuts/#maia-chat-shortcuts) section in *Keyboard Shortcuts*.
-For shortcut keys you can use in the chat, see the [Maia Shortcut Keys](/refguide/keyboard-shortcuts/#maia-chat-shortcuts) section in *Keyboard Shortcuts*. These shortcuts also work in Maia Chat in Studio Pro 11.7 and below.
+For tips on getting better responses, see the [Best Practices](/portal/maia/#best-practices) section in *Maia in Mendix Portal* or the [Text Input](/refguide/maia-make/#text-input) section of *Maia Make Capabilites*.
-For tips on getting better responses, see the [Best Practices](/portal/maia/#best-practices) section in *Maia in Mendix Portal* or the [Text Input](/refguide/maia-make/#text-input) section of *Maia Make Capabilities*.
+### In Studio Pro 11.8 and Above
-## Maia Chat in Studio Pro 11.7 and Below {#maia-chat-legacy}
+In Studio Pro 11.8 and above, Maia Chat is incorporated into the unified Maia Make capabilities, which are enabled by default. Maia Chat does not have a dedicated interface. For more information, see [Maia Make Capabilities](/refguide/maia-make/).
-In Studio Pro 11.7 and below, Maia Chat is a separate chat interface in Studio Pro.
+### In Studio Pro 11.7 and Below
-{{% alert color="info" %}}
-Maia Chat does not use any project, customer, or company information. It only uses the data you enter in the chat to fulfill the request. Do not enter any personal or sensitive data.
-{{% /alert %}}
-
-There are two ways to access Maia Chat in Studio Pro:
+In Studio Pro 11.7 and below, there are two ways to access Maia Chat in Studio Pro:
* Click the **Maia** ({{% icon name="sparkles" %}}) icon to the right of the top bar.
* Go to the **View** menu and click **Maia**.
@@ -54,9 +56,7 @@ The chat interface appears on the right side of Studio Pro under the **Maia** pa
{{< figure src="/attachments/refguide/mendix-ai-assistance/maia-make/maia-chat/maia-chat-interface.png" alt="" width="250px">}}
-You can start using Maia Chat by clicking one of the demo questions. Alternatively, you can ask your own question, and press Enter or click **Ask** to send the question.
-
-### Giving Feedback {#feedback}
+#### Giving Feedback {#feedback}
Mendix encourages you to provide feedback on Maia Chat answers to help improve the feature.
@@ -71,5 +71,4 @@ Click **Submit feedback** to send your feedback. Maia Chat then returns you to t
## Read More
-* [Maia Make Capabilities](/refguide/maia-make/)
-* [Maia Learn](/refguide/maia-learn/)
+The **Maia** pane also includes a **Learn** tab. For more information, see [Maia Learn](/refguide/maia-learn/).
diff --git a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-explain.md b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-explain.md
index f661a08db83..4fc5a2b0b6c 100644
--- a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-explain.md
+++ b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-explain.md
@@ -12,8 +12,6 @@ description: "Describes the features in Maia Explain."
To use Maia Explain, you need an internet connection and must be signed in to Studio Pro.
{{% /alert %}}
-Maia Explain helps you understand existing documents in your app, such as microflows and pages. It describes the overall purpose of a document and highlights its technical details. Use Maia Explain when you take over an app from another developer, before you change existing logic, or when you review documents that Maia generated.
-
## Using Maia Explain
The initial answer consists of two parts:
@@ -54,10 +52,10 @@ Studio Pro sends a message to Maia, and a chat interface with an initial answer
{{< figure src="/attachments/refguide/mendix-ai-assistance/maia-make/maia-explain/maia-explain-interface.png" alt="" width="300px">}}
{{% alert color="info" %}}
-Only requests related to Maia Explain are properly handled in this chat. If you have other questions, close this chat and go back to the general [Chat](/refguide/maia-chat/) interface.
+In this dedicated chat, only requests related to Maia Explain are properly handled. If you have other questions, close this chat and go back to the general [Maia Chat](/refguide/maia-chat/) interface.
{{% /alert %}}
## Read More
* [Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/)
-* [Chat with Maia](/refguide/maia-chat/)
+* [Maia Chat](/refguide/maia-chat/)
diff --git a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-for-domain-model.md b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-for-domain-model.md
index 59d23f5fb62..598d0c1bc06 100644
--- a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-for-domain-model.md
+++ b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-for-domain-model.md
@@ -1,9 +1,8 @@
---
-title: "Domain Models in Maia Make"
-linktitle: "Domain Models"
+title: "Maia for Domain Model"
url: /refguide/maia-for-domain-model/
weight: 50
-description: "Describes how Maia Make generates, explains, and improves domain models in Studio Pro."
+description: "Describes the features in Maia for Domain Model."
aliases:
- /refguide/domain-model-generator/
#If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the product. See Mapping to Products for more details.
@@ -12,24 +11,22 @@ aliases:
## Introduction
{{% alert color="info" %}}
-In Studio Pro 11.8 and above, domain model generation is part of [Maia Make](/refguide/maia-make/). In Studio Pro 11.7 and below, it is a separate tool called Maia for Domain Model.
-
-To use this capability, you need an internet connection and must be signed in to Studio Pro.
+To use Maia for Domain Model, you need an internet connection and must be signed in to Studio Pro.
{{% /alert %}}
-Maia can generate new [domain models](/refguide/domain-model/) and explain and improve existing domain models. You can work on the domain model in the same conversation in which you create pages, logic, and other parts of your app. For information on the current limitations, see the [Limitations](#limitation) section below.
+Maia for Domain Model helps you generate new [domain models](/refguide/domain-model/) and explain and improve existing domain models. It has some limitations. For more information, see the [Limitations](#limitation) section below.
-## Working with Domain Models in Maia
+## Using Maia for Domain Model
Describe your application or its main goals in the chat. Maia uses this information to generate a relevant domain model for you. In Studio Pro 11.1 and above, you can also attach up to one image and one PDF to help Maia better understand your request. For more information, see the [Attachment Requirements](#attachment-requirements) section below.
-After Maia generates a domain model, you can continue asking Maia to add entities and associations to the domain model. Maia also supports adding more attributes to an existing entity in the domain model. You can also ask Maia to explain or improve the generated domain model.
+After Maia generates a domain model, if the dedicated chat is still active, you can continue asking Maia to add entities and associations to the domain model. Maia also supports adding more attributes to an existing entity in the domain model. You can also ask Maia to explain or improve the generated domain model.
### In Studio Pro 11.8 and Above
-In Studio Pro 11.8 and above, you can work on domain models with Maia in the **Chat** tab, which is enabled by default. There is no dedicated interface for domain models. For more information, see [Maia Make Capabilities](/refguide/maia-make/).
+In Studio Pro 11.8 and above, Maia for Domain Model is incorporated into the unified Maia Make capabilities, which are enabled by default. Maia for Domain Model does not have a dedicated interface. For more information, see [Maia Make Capabilities](/refguide/maia-make/).
-### Maia for Domain Model in Studio Pro 11.7 and Below
+### In Studio Pro 11.7 and Below
In Studio Pro 11.7 and below, Maia for Domain Model is enabled by default. You can find it in the toolbar of a domain model:
@@ -46,7 +43,7 @@ Maia for Domain Model does not support deleting items in the domain model. You c
{{% /alert %}}
{{% alert color="info" %}}
-In this dedicated chat, only requests related to the domain model are handled. If you have other questions, close this chat and go back to the general [Chat](/refguide/maia-chat/) interface.
+In this dedicated chat, only requests related to the domain model are handled. If you have other questions, close this chat and go back to the general [Maia Chat](/refguide/maia-chat/) interface.
{{% /alert %}}
#### Attachment Requirements {#attachment-requirements}
@@ -60,14 +57,13 @@ In Studio Pro 11.1 and above, Maia for Domain Model supports adding up to one im
## Limitations {#limitation}
-Maia has the following limitations when it works with domain models:
+Maia for Domain Model has the following limitations:
* It can only generate an attribute of type Enumeration if there is an existing enumeration in the module to refer to.
* It cannot set [generalization](/refguide/generalization-and-association/) for an entity.
## Read More
-* [Maia Make Capabilities](/refguide/maia-make/)
* [Data in the Domain Model](/refguide/domain-model/)
* [Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/)
-* [Chat with Maia](/refguide/maia-chat/)
+* [Maia Chat](/refguide/maia-chat/)
diff --git a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-for-oql.md b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-for-oql.md
index 5bd19cee3e5..a07577b1680 100644
--- a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-for-oql.md
+++ b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-for-oql.md
@@ -1,22 +1,19 @@
---
-title: "OQL in Maia Make"
-linktitle: "OQL"
+title: "Maia for OQL"
url: /refguide/maia-for-oql/
weight: 78
-description: "Describes how Maia Make generates OQL queries for view entities in Studio Pro."
+description: "Describes the features in Maia for OQL Generation."
---
## Introduction
{{% alert color="info" %}}
-In Studio Pro 11.9 and above, OQL generation is part of [Maia Make](/refguide/maia-make/). In Studio Pro 11.8 and below, it is a separate tool called Maia for OQL.
-
-To use this capability, you need an internet connection and must be signed in to Studio Pro.
+To use Maia for OQL, you need an internet connection and must be signed in to Studio Pro.
{{% /alert %}}
-Maia can generate and manage OQL (Object Query Language) queries. This simplifies query creation and reduces manual effort. For information on the current limitations, see the [Limitations](#limitations) section below.
+Maia for OQL enables you to generate and manage OQL (Object Query Language) queries. It simplifies query creation and reduces manual effort. It has some limitations. For more details, see the [Limitations](#limitations) section below.
-## Working with OQL in Maia
+## Using Maia for OQL
Describe the data you need. For example, if you type *Show all active orders with customer names*, Maia generates the most relevant OQL query based on the data available in the same module.
@@ -24,13 +21,13 @@ Maia interprets your intent and provides a query that fits your requirements, he
### In Studio Pro 11.9 and Above
-In Studio Pro 11.9 and above, you can generate OQL queries with Maia in the **Chat** tab, which is enabled by default. There is no dedicated interface for OQL. For more information, see [Maia Make Capabilities](/refguide/maia-make/).
+In Studio Pro 11.9 and above, Maia for OQL is incorporated into the unified Maia Make capabilities, which are enabled by default. Maia for OQL does not have a dedicated interface. For more information, see [Maia Make Capabilities](/refguide/maia-make/).
{{% alert type="info" %}}
Studio Pro 11.13 and above, and 11.12.2 and above, include a setting to enable or disable OQL generation with Maia. OQL generation always uses the Mendix Platform regardless of the configured AI provider. To use OQL generation, you must enable both **Enable Maia** and **Enable OQL Tool**.
{{% /alert %}}
-### Maia for OQL in Studio Pro 11.8 and Below
+### In Studio Pro 11.8 and Below
In Studio Pro 11.8 and below, to enable Maia for OQL, go to **Edit** > **Preferences** > the **Maia** tab and select **Enable Maia for OQL Generation**.
@@ -44,9 +41,9 @@ Clicking **Maia for OQL** opens a dedicated chat interface on the right side of
## Limitations {#limitations}
-OQL generation with Maia has the following limitations:
+Maia for OQL has the following limitations:
-* It currently supports only [view entities](/refguide/view-entities/).
+* Maia for OQL currently supports only [view entities](/refguide/view-entities/).
* Associations with a **custom name** are not supported.
* Cross-module associations are not supported.
* The chat history does not retain previous OQL examples.
diff --git a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-for-pages.md b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-for-pages.md
index 0bbfab7df1e..46838df5fa6 100644
--- a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-for-pages.md
+++ b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-for-pages.md
@@ -1,9 +1,8 @@
---
-title: "Pages in Maia Make"
-linktitle: "Pages"
+title: "Maia for Pages"
url: /refguide/maia-for-pages/
weight: 60
-description: "Describes how Maia Make generates, changes, and explains pages in Studio Pro."
+description: "Describes the features in Maia for Pages."
aliases:
- /refguide/page-generator/
#If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the product. See Mapping to Products for more details.
@@ -12,30 +11,28 @@ aliases:
## Introduction
{{% alert color="info" %}}
-In Studio Pro 11.8 and above, page generation is part of [Maia Make](/refguide/maia-make/). In Studio Pro 11.7 and below, it is a separate tool called Maia for Pages.
-
-To use this capability, you need an internet connection and must be signed in to Studio Pro.
+To use Maia for Pages, you need an internet connection and must be signed in to Studio Pro.
{{% /alert %}}
-Maia can generate a [page](/refguide/page/) by adding and configuring widgets based on text input and optional image input. You can also ask Maia to edit or remove existing widgets, or to provide further improvements and explanations. You can work on pages in the same conversation in which you create the domain model, logic, and other parts of your app. For information on the current limitations, see the [Limitations](#limitation) section below.
+Maia for Pages helps you generate a [page](/refguide/page/) by adding and configuring widgets based on text input and optional image input. You can also use it to edit or remove existing widgets or ask it to provide further improvements and explanations. For information on the current limitations of Maia for Pages, see the [Limitations](#limitation) section below.
-## Working with Pages in Maia
+## Using Maia for Pages
Describe your page or its main goals in the chat. Maia uses this information to add relevant widgets to the page and configure them for you. When generating a page, Maia knows about the domain model of the module you are currently working on. For example, it might include a [Data View](/refguide/data-view/) with some [Text Box](/refguide/text-box/) widgets for an attribute of an entity.
You can also supplement text input with an image. Maia uses the image to interpret your request better. For example, it can recognize the layout of a page from the image and replicate it. The image can be a screenshot, photo, wireframe, or drawing. With text input, you can also specify differences between the provided image and how you would like the generated page to appear. For example, you might write: *Generate a page based on this image, but change the header to Welcome.*
-On pages that have already been created, either by Maia or manually, you can ask Maia to further improve the page and provide explanations. For example, you can add extra widgets, edit widgets by changing their properties, or remove widgets.
+On pages that have already been created, either by Maia for Pages or manually, you can ask Maia to further improve the page and provide explanations. For example, you can add extra widgets, edit widgets by changing their properties, or remove widgets.
### In Studio Pro 11.8 and Above
-In Studio Pro 11.8 and above, you can work on pages with Maia in the **Chat** tab, which is enabled by default. There is no dedicated interface for pages. For more information, see [Maia Make Capabilities](/refguide/maia-make/).
+In Studio Pro 11.8 and above, Maia for Pages is incorporated into the unified Maia Make capabilities, which are enabled by default. Maia for Pages does not have a dedicated interface. For more information, see [Maia Make Capabilities](/refguide/maia-make/).
In Studio Pro 11.8, only overview pages can be generated.
In Studio Pro 11.9 and above, you can generate custom pages from scratch and modify existing pages. Local variables, additional data sources, client actions, XPath constraints, and expressions are also supported.
-### Maia for Pages in Studio Pro 11.7 and Below
+### In Studio Pro 11.7 and Below
In Studio Pro 11.7 and below, to enable Maia for Pages, go to **Edit** > **Preferences** > the **Maia** tab and select **Enable Maia for Pages**.
@@ -52,12 +49,12 @@ After clicking **Maia for Pages**, a dedicated chat interface appears on the rig
{{< figure src="/attachments/refguide/mendix-ai-assistance/maia-make/maia-for-pages/chat-interface.png" alt="" max-width=42% >}}
{{% alert color="info" %}}
-In this dedicated chat, only requests related to Pages are handled. If you have other questions, close this chat and go back to the general [Chat](/refguide/maia-chat/) interface.
+In this dedicated chat, only requests related to Pages are handled. If you have other questions, close this chat and go back to the general [Maia Chat](/refguide/maia-chat/) interface.
{{% /alert %}}
## Limitations {#limitation}
-Maia does not support all widgets when it generates pages.
+Maia for Pages does not support all widgets.
The following widgets are supported:
@@ -87,7 +84,6 @@ In Studio Pro 11.6 and above, Maia can understand customized pluggable widgets w
## Read More
-* [Maia Make Capabilities](/refguide/maia-make/)
* [Pages](/refguide/page/)
* [Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/)
-* [Chat with Maia](/refguide/maia-chat/)
+* [Maia Chat](/refguide/maia-chat/)
diff --git a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-for-workflows.md b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-for-workflows.md
index b7da9764705..ec6d7bda4cd 100644
--- a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-for-workflows.md
+++ b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-for-workflows.md
@@ -1,23 +1,20 @@
---
-title: "Workflows in Maia Make"
-linktitle: "Workflows"
+title: "Maia for Workflows"
url: /refguide/maia-for-workflows/
weight: 75
-description: "Describes how Maia Make generates, explains, and improves workflows in Studio Pro."
+description: "Describes the features in Maia for Workflows."
#If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the product. See Mapping to Products for more details.
---
## Introduction
{{% alert color="info" %}}
-In Studio Pro 11.9 and above, workflow generation is part of [Maia Make](/refguide/maia-make/). In Studio Pro 11.7 and below, it is a separate tool called Maia for Workflows.
-
-To use this capability, you need an internet connection and must be signed in to Studio Pro.
+To use Maia for Workflows, you need an internet connection and must be signed in to Studio Pro.
{{% /alert %}}
-Maia can generate a [workflow](/refguide/workflows/). It can also provide explanations or suggest improvements to the generated elements. You can work on workflows in the same conversation in which you create the domain model, pages, logic, and other parts of your app. For information on the current limitations, see the [Limitations](#limitation) section below.
+Maia for Workflows helps you generate a [workflow](/refguide/workflows/). It can also provide explanations or suggest improvements to the generated elements. It has some limitations. For more details, see the [Limitations](#limitation) section below.
-## Working with Workflows in Maia
+## Using Maia for Workflows
Describe a business process you want to model. Maia uses this information to add relevant workflow activities and configures them where possible. For more information on how to communicate with Maia to achieve better results when configuring a workflow, see the [Best Practices](/refguide/maia-make/#workflows-best-practices) section of *Maia Make Capabilities*.
@@ -25,15 +22,15 @@ Describe a business process you want to model. Maia uses this information to add
#### Studio Pro 11.9 and Above
-You work on workflows with [Maia](/refguide/maia-make/) in the **Chat** tab, which is enabled by default.
+Maia for Workflows is incorporated into the unified [Maia Make Capabilities](/refguide/maia-make/), which are enabled by default.
#### Studio Pro 11.8
-Workflow generation is not available.
+Maia for Workflows is not available.
#### Studio Pro 11.7 and Below
-In Studio Pro 11.7 and below, workflow generation is a separate tool called Maia for Workflows. To enable Maia for Workflows, go to **Edit** > **Preferences** > the **Maia** tab and select **Enable Maia for Workflows**. After you enable it, you can find it in the toolbar of a workflow:
+To enable Maia for Workflows, go to **Edit** > **Preferences** > the **Maia** tab and select **Enable Maia for Workflows**. After you enable it, you can find it in the toolbar of a workflow:
{{< figure src="/attachments/refguide/mendix-ai-assistance/maia-make/maia-for-workflows/maia-for-workflows.png" alt="" max-width=80% >}}
@@ -55,4 +52,4 @@ Due to the complex cross-document nature of a workflow, not all properties of th
* [Maia Make Capabilities](/refguide/maia-make/)
* [Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/)
* [Workflow](/refguide/workflows/)
-* [Chat with Maia](/refguide/maia-chat/)
+* [Maia Chat](/refguide/maia-chat/)
diff --git a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-mcp.md b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-mcp.md
index 128c87d3987..7bd3857dfbc 100644
--- a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-mcp.md
+++ b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-mcp.md
@@ -23,7 +23,7 @@ For details on the current limitations, see the [Limitations](#limitations) sect
There are two ways to open the MCP Client panel:
-* Open the **Chat** tab in the **Maia** pane, then click **Configure MCP Connections** ({{% icon name="plug" %}}).
+* Click the **Configure MCP Connections** ({{% icon name="plug" %}}) icon under the **Maia Chat** tab.
* Go to the **View** menu and click **MCP Settings**.
### Preset Servers {#preset-servers}
@@ -169,4 +169,4 @@ Maia MCP Client has the following limitations:
## Read More
* [Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/)
-* [Chat with Maia](/refguide/maia-chat/)
+* [Maia Chat](/refguide/maia-chat/)
diff --git a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-plan-mode.md b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-plan-mode.md
new file mode 100644
index 00000000000..194d7873c22
--- /dev/null
+++ b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-plan-mode.md
@@ -0,0 +1,64 @@
+---
+title: "Maia Plan Mode"
+linktitle: "Plan Mode"
+url: /refguide/maia-plan-mode/
+weight: 95
+description: "Describes how to use the planning features in Maia agent."
+---
+
+## Introduction
+
+{{% alert color="info" %}}
+This feature is part of [Maia Make](/refguide/maia-make/) and was introduced in Studio Pro 11.16.
+
+To use Plan Mode, you need an internet connection and must be signed in to Studio Pro. This feature is **not** available when using the Studio Pro MCP server mode. Instead, you should use the native planning features of the agent
+that connects to Studio Pro.
+{{% /alert %}}
+
+Maia Plan Mode helps you plan the implementation of an entire app or a large feature before making changes. Maia creates a plan that you can review and edit (potentially using Maia) before starting implementation.
+
+You can also use the plan to track progress and continue implementation in a new chat session.
+
+## Creating a Plan
+
+When you ask Maia to implement an entire app or a large feature that spans several documents or modules, Maia asks whether you want to enter Plan Mode.
+
+If you agree, Maia reads the open app, gathers the context needed for your request, and writes an implementation plan. In Plan Mode, Maia can only read the open app and write a plan document.
+
+The plan is a Markdown file stored at `maia/plans//plan.md` in your application directory.
+
+## Reviewing and Implementing a Plan
+
+After creating a plan, Maia asks you to review it. To review the plan and start implementation, follow these steps:
+
+1. In the **App Explorer**, expand **App** > **Maia** > **plans** and select the plan.
+2. Review the plan. Edit it yourself or ask Maia to make changes. Make sure any manual changes are saved.
+3. When you are satisfied with the plan, confirm Maia's request to exit Plan Mode and start implementation.
+
+## Tracking Progress
+
+The plan remains available in your application after Maia implements part or all of it.
+
+To pause implementation and continue in a new session, follow these steps:
+
+1. Stop Maia during implementation.
+2. Ask Maia to record the progress made in the plan.
+3. Start a new chat session and ask Maia to continue implementing the plan.
+
+## Manually Entering Plan Mode
+
+Maia input box now contains the **Plan Mode** button. By pressing the **Plan Mode** button you can enter the plan mode manually.
+This signals to Maia that you are planning to implement a larger feature and will allow Maia only to read the app and eventually
+write a plan.
+
+## Limitations
+
+* Only Maia can create plans. You can edit a plan after Maia creates it.
+* Maia cannot delete plans. You can delete them yourself.
+
+## Read More
+
+* [Maia Make Capabilities](/refguide/maia-make/)
+* [Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/)
+* [Maia Chat](/refguide/maia-chat/)
+* [AI SDLC playbook](https://claude.com/resources/articles/the-ai-native-sdlc-playbook)
\ No newline at end of file
diff --git a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-web-fetch.md b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-web-fetch.md
index ffd1eb4d5c8..0aa8623b494 100644
--- a/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-web-fetch.md
+++ b/content/en/docs/refguide/mendix-ai-assistance/maia-make/maia-web-fetch.md
@@ -58,4 +58,4 @@ If Maia says it cannot fetch a URL, check the following:
* [Maia Make Capabilities](/refguide/maia-make/)
* [Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/)
-* [Chat with Maia](/refguide/maia-chat/)
+* [Maia Chat](/refguide/maia-chat/)
diff --git a/content/en/docs/refguide/mendix-ai-assistance/maia-make/studio-pro-mcp-server.md b/content/en/docs/refguide/mendix-ai-assistance/maia-make/studio-pro-mcp-server.md
index 159ad006a3b..279779ad73f 100644
--- a/content/en/docs/refguide/mendix-ai-assistance/maia-make/studio-pro-mcp-server.md
+++ b/content/en/docs/refguide/mendix-ai-assistance/maia-make/studio-pro-mcp-server.md
@@ -12,7 +12,7 @@ description: "Describes the features in Studio Pro MCP Server."
{{% alert color="info" %}}
This feature is available from Studio Pro 11.10.
-To use Studio Pro MCP Server, you need an internet connection. The MCP Server runs locally on your workstation, so you do not need to be signed in to Studio Pro to use it. To use Mendix platform MCP servers, such as [Maia Plan as MCP Server](/developerportal/maia-plan-mcp/), you need to authenticate with your Mendix account.
+To use Studio Pro MCP Server, you need an internet connection and must be signed in to Studio Pro.
{{% /alert %}}
Studio Pro MCP Server enables bring your own agent (BYO Agent) capabilities, allowing you to use Maia's capabilities directly from external clients, including AI coding assistants, agents, and other MCP-based LLM tools.
@@ -22,31 +22,10 @@ It has the following highlights:
* Full Maia feature parity – The MCP Server exposes the same capabilities that Maia offers within Studio Pro.
* Live updates – Any changes made through Maia via the MCP Server are reflected in real time within Studio Pro.
-For an overview of how Maia works with external AI tools, see [Using Maia with External AI Agents](/refguide/maia-external-agents/).
-
{{% alert color="info" %}}
When you connect external agents or AI tools to Studio Pro's MCP Server, those tools consume tokens from your own LLM provider account each time they interact with Maia. Because these requests occur outside of the Mendix environment, usage and billing details are managed through your LLM provider's dashboard rather than within Mendix.
{{% /alert %}}
-## How It Works {#how-it-works}
-
-The Studio Pro MCP Server runs on your workstation as part of Studio Pro. It works in the following way:
-
-1. You enable the MCP Server in Studio Pro and connect your external client to it on `localhost`.
-2. Your external client sends a request to its own LLM, which decides to use one of the tools the MCP Server exposes.
-3. The MCP Server carries out the request with Maia capabilities on the app that is open in Studio Pro.
-4. Studio Pro shows the changes in real time. You can review them in the regular editors and in the **Errors** pane.
-
-The external client works with Mendix documents, such as domain models and microflows, through the tools the MCP Server exposes.
-
-## Use Cases {#use-cases}
-
-Use the Studio Pro MCP Server in the following situations:
-
-* You use an AI coding assistant for other work, such as code in other repositories, documentation, or tickets. With the MCP Server, you can use the same assistant for your Mendix app.
-* Your agent has access to other MCP servers, such as [Maia Plan as MCP Server](/developerportal/maia-plan-mcp/). The agent can use information from these sources, then change your app through the Studio Pro MCP Server.
-* You need an alternative to Maia Units. Requests from an external client use your own LLM provider account. For more information, see the [Maia Usage Limits](/refguide/mendix-ai-assistance/#maia-usage) section of *Mendix AI Assistance (Maia)*.
-
## Enabling the MCP Server
To enable the MCP Server, go to **Preferences** > **AI** > **MCP Server** and select **Enable MCP Server**. You can also configure the port in this menu.
@@ -59,17 +38,6 @@ Once enabled, you can connect external clients to the MCP Server. For example, t
Replace `` with your preferred server name and `` with the port configured in **Preferences**.
-## Working Practices {#working-practices}
-
-The following practices help you get reliable results when using an external client:
-
-* Give the agent context. [Agent Instructions (AGENTS.md)](/refguide/maia-agent-instructions/) and [Agent Skills (SKILLS.md)](/refguide/maia-agent-skills/) follow industry standards, so they work with Maia and other agentic tools. Use them to share your conventions with every agent that works on the app.
-* Keep requests small. Ask for one feature or one story at a time so you can review each change.
-* Check the changed documents and the **Errors** pane before you continue with the next request.
-* Commit the changes to version control when you have reviewed and tested them.
-
-For more practices, see the [Working Practices for Agentic Development](/refguide/agentic-development/#working-practices) section of *Agentic and Model-Driven Development*.
-
## Limitations
The following limitations apply only to Studio Pro 11.10:
@@ -79,8 +47,6 @@ The following limitations apply only to Studio Pro 11.10:
## Read More
-* [Using Maia with External AI Agents](/refguide/maia-external-agents/)
* [Maia Make Capabilities](/refguide/maia-make/)
-* [Maia MCP Client](/refguide/maia-mcp/)
* [Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/)
-* [Chat with Maia](/refguide/maia-chat/)
+* [Maia Chat](/refguide/maia-chat/)
diff --git a/content/en/docs/refguide/mendix-ai-assistance/start-with-maia.md b/content/en/docs/refguide/mendix-ai-assistance/start-with-maia.md
index 7f37d19a765..de4cc067013 100644
--- a/content/en/docs/refguide/mendix-ai-assistance/start-with-maia.md
+++ b/content/en/docs/refguide/mendix-ai-assistance/start-with-maia.md
@@ -60,4 +60,4 @@ You can attach a maximal of one image or one PDF and the attachment must meet th
## Read More
* [Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/)
-* [Chat with Maia](/refguide/maia-chat/)
+* [Maia Chat](/refguide/maia-chat/)
diff --git a/content/en/docs/refguide/mendix-ai-assistance/translation-generator.md b/content/en/docs/refguide/mendix-ai-assistance/translation-generator.md
index 9dec68a03b0..49e50a8bca1 100644
--- a/content/en/docs/refguide/mendix-ai-assistance/translation-generator.md
+++ b/content/en/docs/refguide/mendix-ai-assistance/translation-generator.md
@@ -13,8 +13,6 @@ To use Translation Generator, an internet connection and signing in to Studio Pr
Maia Translation Generator is a translation tool powered by AI in Mendix Studio Pro. You can use this AI tool in Studio Pro to [batch translate](/refguide/batch-translate/) your Mendix app into a different language. You can also use it to translate [system texts](/refguide/system-texts/).
-In Studio Pro 11.15 and above, you can also ask Maia in the [Maia](/refguide/maia-make/) chat interfact to create and update translations, as part of the same conversation in which you build a feature.
-
For more information on how to enable and use this AI translation tool in Studio Pro, see the sections below.
## Modeling Using Translation Generator
diff --git a/content/en/docs/refguide/modeling/domain-model/_index.md b/content/en/docs/refguide/modeling/domain-model/_index.md
index 468a945cd7f..a98e770ca84 100644
--- a/content/en/docs/refguide/modeling/domain-model/_index.md
+++ b/content/en/docs/refguide/modeling/domain-model/_index.md
@@ -116,4 +116,4 @@ The entity `OrderLine` is stored in the table `module$orderline` which is shown
## Read More
* [Configuring a Domain Model](/refguide/configuring-a-domain-model/)
-* [Domain Models in Maia Make](/refguide/maia-for-domain-model/)
+* [Maia for Domain Model](/refguide/maia-for-domain-model/)
diff --git a/content/en/docs/refguide/modeling/domain-model/entities/view-entities/_index.md b/content/en/docs/refguide/modeling/domain-model/entities/view-entities/_index.md
index 577e7e30e3f..ba789620f7c 100644
--- a/content/en/docs/refguide/modeling/domain-model/entities/view-entities/_index.md
+++ b/content/en/docs/refguide/modeling/domain-model/entities/view-entities/_index.md
@@ -72,7 +72,7 @@ Alternatively, you can right-click the view entity and click **Go to OQL query**
The OQL query tab consists of the following sections:
* [OQL editor](#oql-editor)
-* [Generating OQL with Maia](#maia-for-oql)
+* [Maia for OQL](#maia-for-oql)
* [Preview data table](#preview-data)
{{< figure src="/attachments/refguide/modeling/domain-model/view-entities/view-entity-document.png">}}
@@ -131,9 +131,9 @@ FROM Shop.Order AS o
{{< figure src="/attachments/refguide/modeling/domain-model/view-entities/association-alias.png" >}}
-### Generating OQL with Maia {#maia-for-oql}
+### Maia for OQL {#maia-for-oql}
-You can ask Maia to suggest OQL queries for you. For more information, see [OQL in Maia Make](/refguide/maia-for-oql/).
+You can ask Maia to suggest OQL queries for you. For more information, see [Maia for OQL](/refguide/maia-for-oql/).
### Preview Data Table {#preview-data}
diff --git a/content/en/docs/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration.md b/content/en/docs/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration.md
deleted file mode 100644
index 1925e4b2f03..00000000000
--- a/content/en/docs/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration.md
+++ /dev/null
@@ -1,259 +0,0 @@
----
-title: "Best Practices for Asynchronous Job Orchestration"
-linktitle: "Asynchronous Job Orchestration"
-url: /refguide/asynchronous-job-orchestration/
-weight: 20
-description: "Describes best practices for orchestrating long-running asynchronous jobs between Mendix apps and external systems."
----
-
-## Introduction
-
-Mendix provides an extensive toolset for integration between multiple systems, such as REST, OData, or Business Events. You can use these building blocks to organize secure, reliable, and synchronous or asynchronous communication, such as sending requests, listening to events, or transferring data.
-
-This document focuses on a specific use case where one system hands work to another system and observes its completion asynchronously. It assumes long-running external jobs that could fail or be interrupted. A typical case is submitting a request to an external system where completion might take hours or days.
-
-## Prerequisites
-
-Make sure you have access to the following Studio Pro features:
-
-* [Business event services](/refguide/business-event-services/) – available in Studio Pro [9.18](/releasenotes/studio-pro/9.18/) and above. They also require the [Mendix Business Events](/appstore/services/business-events/) module from Mendix Marketplace.
-* The [Notify Workflow](/refguide/notify-workflow/) microflow activity – available in Studio Pro [10.0](/releasenotes/studio-pro/10.0/) and above.
-* [Notification](/refguide/notification/) boundary events – available in Studio Pro [11.11](/releasenotes/studio-pro/11.11/) and above.
-
-## Architecture Overview
-
-This document describes the recommended approach. In some cases, it is reasonable to deviate from it. For example, for small and simple systems that only use Mendix apps, you can combine the domain app and the adapter. The sections below describe the trade-offs of these architectural decisions.
-
-### Layers
-
-The system consists of the following layers:
-
-{{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/architecture-layers.png" alt="Component diagram showing the domain app and adapter Mendix apps communicating through an event broker, and the adapter communicating with the external system through an event broker or REST" >}}
-
-* Domain app – a Mendix app that holds business logic. It orchestrates the processes running inside the app itself and in various external systems.
-* Adapter – a Mendix app that manages the communication between the domain app and the external system. An adapter adds overhead, because it is a separate app that you must build and manage. If there is only a single app or performance is critical, you can include the adapter functionality in the domain app instead. However, an adapter also brings the following advantages, which is why this architecture includes it:
-
- * Promotes loose coupling between the domain app and the external system, which makes it easier and safer to develop the apps independently.
- * Allows better control over integration boundaries, such as security.
- * Helps to manage load redistribution in high-load systems.
-
-* External system – any system (including a Mendix app) that does the work. This work is typically a long-running job that produces decisions, data, or both.
-* Event broker – for event-driven, asynchronous communication between the domain app and the adapter, and optionally between the adapter and the external system. This document uses Mendix Business Events, which the Mendix Event Broker can provide for apps running in Mendix Cloud, or a local broker such as Kafka.
-
-### Use Case: Observing the Completion of a Long-Running Task
-
-The flow to build is as follows:
-
-{{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/long-running-task-flow.png" alt="Sequence diagram of the domain app submitting a task to the adapter, the adapter forwarding it to the external system and acknowledging acceptance, and the external system notifying completion later" >}}
-
-1. The domain app submits a task with a payload.
-2. The adapter forwards the task to the external system.
-3. The adapter acknowledges that the task is accepted and communicates it to the domain app.
-4. After a certain time, the external system completes the task and notifies the adapter.
-5. The adapter sends the task completion event to the domain app.
-
-This flow also handles the following scenarios:
-
-1. The adapter or external system is down at the moment of the request, or goes down mid-execution. The domain app can escalate to the responsible party when the acceptance or completion deadline is exceeded.
-2. The external system refuses work or fails during execution. The adapter can relay the error message back to the domain app.
-3. The domain app sends a cancellation signal.
-
-The following topics are out of scope: handling more than one task type, integrating with multiple external systems, restarting a failed task, security configuration, and message schema versioning.
-
-## Configuration
-
-### Shared Elements
-
-The domain app and the adapter can share certain domain model entities and microflows related to message processing. You can extract them into a separate module and reuse it in both apps. Examples are the **ProcessedMessage** entity and the **SUB_Handle_Event** microflow. To keep each layer's specification complete, this document describes every component and indicates which ones you can share.
-
-{{% alert color="info" %}}
-The names of domain model entities, attributes, microflows, and services are suggestions based on best practices in distributed computing and Mendix development. None of them are mandatory, and you can use your own terminology instead.
-{{% /alert %}}
-
-### Domain App
-
-The domain app is a Mendix app that orchestrates long-running tasks executed by external systems. In this example, it communicates only with the adapter to do the following:
-
-* Publish new task requests
-* Cancel the execution of existing tasks
-* Listen to task completion events
-
-#### Domain Model
-
-{{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-domain-model.png" alt="Domain model of the domain app with the ExternalTask, ProcessedMessage, and OrphanEvent entities and their attributes" >}}
-
-The **ExternalTask** entity is used for tracking a long-running job in the external system.
-
-* **CorrelationId** is a UID owned by the domain app. The domain app creates it before submitting a new task. The **CorrelationId** provides a stable identifier that relates all requests, events, and callbacks to the same business operation.
-* **State** (**Requested**, **Accepted**, **Succeeded**, **Failed**, **Canceled**) reflects the last available execution state of an external job. It is updated when the domain app receives an event from the adapter.
-* **ExecutionDeadline** indicates the time to escalate if the task is not completed yet.
-* **Input** is a payload sent to the external job that contains the required parameters to start and execute the job. These parameters can include the job name and context data, such as object IDs, timestamps, and user input. The shape of the input is app-specific. It can be a list of comma-separated values or a stringified JSON structure. For example, `job_name=my_first_task,target_group=management,item_id=295128537,deadline=1790689440`.
-* **Outcome** is a payload received upon the completion of the task. Its shape is also app-specific, and it can contain either the result of the external job or an error message when the job failed.
-
-The **ProcessedMessage** entity records messages from the adapter that have already been processed. It ensures that the same message is not processed more than once in case of a redelivery. For more details on its purpose and management, see [Message Deduplication and Retention](#deduplication). It requires only one attribute:
-
-* **MessageId** is a UID generated by the adapter in the same transaction that publishes the message.
-
-The remaining attributes are optional and primarily used for auditing:
-
-* **ProcessedAt** is the time when the message was received.
-* **MessageType** (**TaskAccepted**, **TaskCompleted**) is the event type for which the message was sent.
-
-The **OrphanEvent** entity is used to store events received from the adapter that could not be associated with any existing **ExternalTask** by their **CorrelationId**. An orphan event usually indicates a missing **ExternalTask** object or a mistake in the **CorrelationId** value sent by the adapter. Such events need to be investigated and resolved manually.
-
-#### Workflows
-
-A Mendix workflow is a top-level organization facilitator designed to handle long-running tasks. The following example is a reusable workflow that takes an **ExternalTask** as its context object. You can add this workflow to one or several processes (other workflows) as a **Call workflow** activity. The workflow does the following:
-
-* It calls **HandleBE_SubmitTask**, which in turn generates a **CorrelationId** if it does not exist yet and publishes a **SubmitTask** business event for the adapter.
-* After the submission, it schedules a non-interrupting timer boundary event that triggers an escalation microflow if the execution deadline is exceeded, for example, to notify the responsible person or perform automatic actions. You can handle other types of deadlines, such as an acceptance deadline, in a similar way. This example omits them for simplicity.
-* The workflow remains **In Progress** until it receives a completion notification.
-
-{{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-task-workflow.png" alt="Workflow with an ExternalTask context object that publishes SubmitTask, waits for a task completed event, and has boundary events for a deadline exceeded escalation and a cancellation request" >}}
-
-Parent workflows that call this workflow wait for it to finish before continuing. The following example is a process that sequentially starts two asynchronous jobs and waits for them to finish. Every sub-workflow call requires a separate **ExternalTask** context object to submit and track its own asynchronous job instance. You can pass this **ExternalTask** to the sub-workflow call through an association to the parent workflow context object. In this example, the parent workflow has a **WorkflowContext** entity with **WorkflowContext_ExternalTask_A** and **WorkflowContext_ExternalTask_B** associations.
-
-{{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-parent-workflow.png" alt="Parent workflow calling two sub-workflows, External Task A and External Task B, in sequence, alongside a WorkflowContext entity with two associations to ExternalTask" >}}
-
-#### Business Event Services
-
-The domain app can publish two business events: **SubmitTask** and **CancelTask**.
-
-{{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-business-event-service.png" alt="ExternalTask_Commands business event service in Studio Pro with SubmitTask and CancelTask definitions published through the PBE_SubmitTask and PBE_CancelTask entities" >}}
-
-Every business event must carry a **MessageId** for deduplication and a **CorrelationId** to resolve the **TaskCorrelation** tracked by the adapter.
-
-{{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-business-event-entities.png" alt="PBE_SubmitTask entity with MessageId, CorrelationId, and Input attributes, and PBE_CancelTask entity with MessageId, CorrelationId, and Reason attributes" >}}
-
-#### Microflows
-
-Microflows are the main executors of the logic in the app. They verify message fields, retrieve and update relevant data, and publish or handle consumed business events.
-
-The following two microflows, **HandleBE_SubmitTask** and **HandleBE_CancelTask**, publish **SubmitTask** and **CancelTask** business events respectively. Both generate a unique **MessageId** and create the business event objects to publish.
-
-The **HandleBE_SubmitTask** microflow also generates and sets the **CorrelationId** on the given **ExternalTask** object. You can call this microflow directly from one or several workflows. The **CorrelationId** acts as a resubmission guard: when it is not set, the task is new and is submitted; when it is already set, the task has already been submitted and the microflow does nothing.
-
-{{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-handle-submit-task.png" alt="HandleBE_SubmitTask microflow that checks whether a CorrelationId exists, generates a random hash for the CorrelationId and MessageId, creates a PBE_SubmitTask object, and publishes the business event" >}}
-
-{{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-handle-cancel-task.png" alt="HandleBE_CancelTask microflow that generates a random hash for the MessageId, creates a PBE_CancelTask object from the CorrelationId and Reason parameters, and publishes the business event" >}}
-
-A reusable **SUB_Handle_Event** microflow handles the consumed business events, **TaskAccepted** and **TaskCompleted**, in a similar way. First, it checks whether a business event with the given **MessageId** has already been processed. If so, it is a redelivery and the microflow returns empty to indicate that no action follows. If the message has not been processed yet, it is saved as a **ProcessedMessage**, the **ExternalTask** is retrieved by **CorrelationId**, and if one is found, its state is updated and it is returned from the microflow. If it finds no **ExternalTask** with the given **CorrelationId**, it stores the message as an **OrphanEvent** to be resolved later.
-
-{{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-sub-handle-event.png" alt="SUB_Handle_Event microflow that checks for an already processed message, creates a ProcessedMessage, retrieves the ExternalTask by CorrelationId, and either changes its state or creates an OrphanEvent" >}}
-
-After you import the AsyncAPI YAML for **ExternalTask_Events** from the adapter, you can subscribe to the **TaskAccepted** and **TaskCompleted** business events, which adds the **HandleBE_TaskAccepted** and **HandleBE_TaskCompleted** microflows, respectively.
-
-The **HandleBE_TaskAccepted** microflow maps the required parameters, such as **MessageId**, **CorrelationId**, and **Outcome**, sets the **ExternalTaskState** to **Accepted** and the **ProcessedMessageType** to **TaskAccepted**, and calls the **SUB_Handle_Event** microflow.
-
-{{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-handle-task-accepted.png" alt="HandleBE_TaskAccepted microflow calling SUB_Handle_Event, with the Edit Call Microflow dialog showing the parameter mapping from the PBE_TaskAccepted business event" >}}
-
-The **HandleBE_TaskCompleted** microflow maps the parameters in a similar way, setting the **ExternalTaskState** to **Succeeded**, **Failed**, or **Canceled** and the **ProcessedMessageType** to **TaskCompleted**. The handler also retrieves all workflows that use the **ExternalTask** as their context object and notifies them about the task completion.
-
-{{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-handle-task-completed.png" alt="HandleBE_TaskCompleted microflow calling SUB_Handle_Event, retrieving workflows for the ExternalTask and notifying them, with the parameter mapping expression that converts the completion status into an ExternalTaskState" >}}
-
-### Adapter
-
-The adapter is a Mendix app that manages the communication between the domain app and the external system. This section focuses on the part where the adapter connects with the domain app. The communication between the adapter and the external system is described in [External System](#external-system).
-
-#### Domain Model {#adapter-domain-model}
-
-{{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-domain-model.png" alt="Domain model of the adapter with the TaskCorrelation, ProcessedMessage, and OrphanCallback entities and their attributes" >}}
-
-The **TaskCorrelation** entity stores a reference between the **CorrelationId** received from the domain app and the **VendorJobId** received from the external system. **ProcessingStage** (**Received**, **Submitted**, **Completed**) indicates the execution stage of the external job. You can use it for auditing, retrying after a failure, or filtering records to prune.
-
-The **ProcessedMessage** entity has the same goal as the entity with the same name in the domain app: to ensure that the same message is not processed more than once. You can extract the **ProcessedMessage** entity into a separate module and reuse it in both the domain app and the adapter.
-
-The **OrphanCallback** entity has the same role as the **OrphanEvent** entity in the domain app. However, it stores events that came from the external system and do not have a **TaskCorrelation** with the corresponding **VendorJobId**. Depending on the external system configuration, these can also be callbacks, hence the name. This can happen if a **TaskCorrelation** object was dropped or the external system sent an event for an untracked job. In any case, you need to resolve such an orphan callback manually.
-
-#### Business Event Services {#adapter-business-event-services}
-
-The adapter can publish two business events: **TaskAccepted** and **TaskCompleted**.
-
-{{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-business-event-service.png" alt="ExternalTask_Events business event service in Studio Pro with TaskAccepted and TaskCompleted definitions published through the PBE_TaskAccepted and PBE_TaskCompleted entities" >}}
-
-Every business event must carry a **MessageId** for deduplication and a **CorrelationId** to resolve the **ExternalTask** tracked by the domain app.
-
-{{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-business-event-entities.png" alt="PBE_TaskAccepted entity with MessageId and CorrelationId attributes, and PBE_TaskCompleted entity with MessageId, CorrelationId, CompletionStatus, and Outcome attributes" >}}
-
-#### Microflows {#adapter-microflows}
-
-The adapter has microflows, designed similarly to those in the domain app, that handle the other side of the task management. **HandleBE_TaskAccepted** and **HandleBE_TaskCompleted** publish **TaskAccepted** and **TaskCompleted** business events respectively. Both microflows first retrieve the **TaskCorrelation** object by **VendorJobId**. If none is found, they register an **OrphanCallback** from the external system to be resolved later. If the correlation is found, its **CorrelationId**, together with a generated unique **MessageId** and an optional payload, is written to the business event objects to be published.
-
-{{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-handle-task-accepted.png" alt="Adapter HandleBE_TaskAccepted microflow that retrieves the TaskCorrelation by VendorJobId, creates an OrphanCallback when none exists, and otherwise creates and publishes a PBE_TaskAccepted business event" >}}
-
-{{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-handle-task-completed.png" alt="Adapter HandleBE_TaskCompleted microflow that retrieves the TaskCorrelation by VendorJobId, creates an OrphanCallback when none exists, and otherwise creates and publishes a PBE_TaskCompleted business event" >}}
-
-A reusable **SUB_Handle_Command** microflow handles the consumed business events from the domain app. It follows logic similar to **SUB_Handle_Event** in the domain app. It creates a new **ProcessedMessage** if this is the first time it processes the message, or returns from the microflow otherwise. It then finds the **TaskCorrelation** and updates its **ProcessingStage** if the **TaskCorrelation** already exists, or creates a new **TaskCorrelation** object if this is the first submission of the task.
-
-{{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-sub-handle-command.png" alt="SUB_Handle_Command microflow that checks for an already processed message, creates a ProcessedMessage, and then either changes the ProcessingStage of an existing TaskCorrelation or creates a new one" >}}
-
-Now you can import the AsyncAPI YAML for **ExternalTask_Commands** from the domain app.
-
-The **HandleBE_SubmitTask** and **HandleBE_CancelTask** microflows, which are added during subscription to the corresponding business events, then call the **SUB_Handle_Command** microflow.
-
-{{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-handle-submit-task.png" alt="Adapter HandleBE_SubmitTask microflow calling SUB_Handle_Command, with the Edit Call Microflow dialog showing the parameter mapping from the PBE_SubmitTask business event" >}}
-
-{{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-handle-cancel-task.png" alt="Adapter HandleBE_CancelTask microflow calling SUB_Handle_Command, with the Edit Call Microflow dialog showing the parameter mapping from the PBE_CancelTask business event" >}}
-
-### External System {#external-system}
-
-The previous sections cover only the communication between the domain app and the adapter. How the adapter works with the external system depends on the capabilities of the external system. There are two general cases:
-
-* The external system has event broker capabilities, which allows fully event-driven communication.
-* The external system can only use REST calls or OData actions for request submission and task completion callbacks.
-
-#### Event-Driven Communication with the External System
-
-This is the recommended approach. A fully event-driven approach provides at-least-once delivery guarantees that you would otherwise need to build yourself, and it allows the solution to scale more easily.
-
-A fully event-driven approach also allows you to integrate the adapter into the domain app for small and simple systems. The main role of the adapter is to mitigate the shortcoming of the lack of event-driven communication between the domain app and the external system. For example, the adapter can significantly reduce the risk of message duplication by adding a layer that processes the domain app messages. The duplication risk can never be zero.
-
-For more complex systems, Mendix recommends using the adapter together with event-driven communication. It adds a data resilience and security isolation layer, and it supports scalability.
-
-Fully asynchronous communication between the adapter and the external system is organized the same way as communication between the domain app and the adapter. If the external system is also a Mendix app, the setup is even more similar when you use Business Events:
-
-* The adapter publishes **SubmitTask** and **CancelTask** events with a unique **MessageId**.
-* The external system deduplicates on **MessageId** by verifying that there is no **ProcessedMessage** yet. This means the system must store a list of already processed messages. For more details on the purpose and management of processed messages, see [Message Deduplication and Retention](#deduplication).
-* The external system starts the work and publishes **TaskAccepted** and later **TaskCompleted** events with the results.
-* The adapter consumes the callback events from the external system and relays them to the domain app.
-
-In this architecture, only the adapter knows the external system authentication and **VendorJobId**. The domain app has no access to them.
-
-If the adapter or external system fails, you might need to reconcile already executed events. You can do this by replaying the already received messages. A unique **MessageId** prevents the same work from being done more than once. If the **CorrelationId** is lost, however, you need to reconcile manually by correlating the records yourself.
-
-#### REST or OData Communication with the External System
-
-Not all systems have event broker capabilities. However, almost every system supports REST or OData for synchronous request/response communication with other systems. In this case, communication between the adapter and the external system is one way: the adapter sends a REST call to the external system to start the work, and later the external system sends a similar REST call back to the adapter to communicate acceptance or completion of the work. In this pipeline, you must either accept certain aspects that an event broker manages as costs or build them manually:
-
-* At-least-once delivery – the event broker usually guarantees it, while a REST call can fail and needs an additional retry mechanism to ensure delivery. This applies to both the incoming calls to the external system and the callbacks from the external system.
-* Buffering and load balancing – much easier to set up and manage with an event broker.
-* Additional debugging capabilities, such as message replay.
-
-{{% alert color="info" %}}
-The REST-based system must also implement message deduplication to ensure the same message is not processed more than once. If the external system does not support deduplication, use an adapter to reduce the risk of duplication.
-{{% /alert %}}
-
-The setup for REST-based communication is similar to the event-based setup. The major difference is that instead of a business event service, you create a published REST service in the adapter and configure its endpoint beforehand, and a consumed REST service linking it to a handler microflow.
-
-## Message Deduplication and Retention {#deduplication}
-
-Every message object in this system contains a mandatory **MessageId** attribute. The **MessageId** ensures idempotency: processing the same message multiple times yields the same effective outcome as processing it once. For example, a redelivery of the same task submission request does not start a duplicate job.
-
-The system stores a record of every consumed **MessageId** upon its first arrival. It then checks every new message against the records to see whether it is the first delivery or a duplicate. You do not need to store the whole message. You need only the **MessageId** for deduplication and **ProcessedAt** for automatic cleanup.
-
-With this approach, the database can grow indefinitely. To prevent this, define a retention window for storing the received messages. Base the retention period on the maximum plausible redelivery window, plus a safety margin. For example, if the system guarantees that messages are not redelivered after more than 7 days, a retention period of 14 days is reasonable. If the system cannot guarantee a maximum redelivery window, or if a message is redelivered much later than the window, the message can be processed twice.
-
-Mendix Business Events accumulates messages that it fails to deliver. It retries the messages at increasing intervals for 48 hours, after which they fail. Therefore, a reasonable retention period is 96 hours.
-
-### Automatic Cleanup
-
-Mendix scheduled events are a good choice for regularly running a cleanup microflow. For example, you can configure a scheduled event with a 96-hour interval that runs the following microflow:
-
-{{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/cleanup-processed-messages.png" alt="Cleanup microflow with a while loop that retrieves a list of expired ProcessedMessage objects, exits when the list is empty, and otherwise deletes the objects in the list" >}}
-
-The cleanup microflow retrieves **ProcessedMessage** objects in batches of 1000, using the XPath constraint `[ProcessedAt < '[%CurrentDateTime%] - 96 * [%HourLength%]']` to select only those processed more than 96 hours ago. It then deletes the retrieved objects, or exits the loop when the list is empty. For better performance, index the **ProcessedAt** attribute.
-
-## Read More
-
-* [Mendix Business Events](/appstore/services/business-events/)
-* [Scheduled Events](/refguide/scheduled-events/)
diff --git a/content/en/docs/refguide/modeling/menus/edit-menu/preferences-dialog.md b/content/en/docs/refguide/modeling/menus/edit-menu/preferences-dialog.md
index 5dfe60aa6f9..4f3ca777d05 100644
--- a/content/en/docs/refguide/modeling/menus/edit-menu/preferences-dialog.md
+++ b/content/en/docs/refguide/modeling/menus/edit-menu/preferences-dialog.md
@@ -115,7 +115,7 @@ In Studio Pro 11.7 and below, the **Generative AI** section contains the followi
* **Enable Start with Maia** – when enabled, you can use the **Start with Maia** starting point in Studio Pro to help you create an app. For more information on how to use this feature, see [Start with Maia](/refguide/start-with-maia/). It is enabled by default.
* **Enable Maia Explain** – when enabled, you can use it to explain a microflow or a nanoflow in the logic editors. For more information, see [Maia Explain](/refguide/maia-explain/). It is enabled by default.
-* **Enable Maia for Domain Model** – when enabled, you can use it to generate a new domain model or to explain and improve an existing one. For more information, see [Domain Models in Maia Make](/refguide/maia-for-domain-model/). It is enabled by default.
+* **Enable Maia for Domain Model** – when enabled, you can use it to generate a new domain model or to explain and improve an existing one. For more information, see [Maia for Domain Model](/refguide/maia-for-domain-model/). It is enabled by default.
* **Enable Maia for OQL Generation** – when enabled, you can use it to generate and manage OQL (Object Query Language) queries through an intuitive interface. For more information, see [Maia for OQL](/refguide/maia-for-oql/). It is disabled by default.
* **Enable Maia for Pages** – when enabled, you can use it to generate a new page or to explain and improve an existing one. For more information, see [Maia for Pages](/refguide/maia-for-pages/). It is disabled by default.
* **Enable Maia for Workflows** – when enabled, you can use it to generate workflows by adding and configuring activities. For more information, see [Maia for Workflows](/refguide/maia-for-workflows/). It is disabled by default.
diff --git a/content/en/docs/refguide/modeling/menus/view-menu/_index.md b/content/en/docs/refguide/modeling/menus/view-menu/_index.md
index 431bb2ed3ee..488d16e6088 100644
--- a/content/en/docs/refguide/modeling/menus/view-menu/_index.md
+++ b/content/en/docs/refguide/modeling/menus/view-menu/_index.md
@@ -111,7 +111,7 @@ The [Integration pane](/refguide/integration-pane/) enables you to browse the [C
### Maia
-The **Maia** pane displays the Maia interface. In this chat, you can create and change parts of your app, and ask questions about app development in Mendix, including how to apply concepts, best practices, and development patterns. For more information, see [Maia Make Capabilities](/refguide/maia-make/). In Studio Pro 11.7 and below, the **Maia** pane displays the Maia Chat interface. For more information, see [Chat with Maia](/refguide/maia-chat/).
+The **Maia** pane displays the Maia Chat interface where you can ask questions about app development in Mendix, including how to apply concepts, best practices, and development patterns. For more information, see [Maia Chat](/refguide/maia-chat/).
### Marketplace
diff --git a/content/en/docs/releasenotes/studio-pro/11/11.15.md b/content/en/docs/releasenotes/studio-pro/11/11.15.md
index b70f8b559b2..73d09b2980a 100644
--- a/content/en/docs/releasenotes/studio-pro/11/11.15.md
+++ b/content/en/docs/releasenotes/studio-pro/11/11.15.md
@@ -50,7 +50,6 @@ You can set the default flow shape for all new sequence flows in the **App setti
* Pluggable widgets can now be translated [using system texts](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis/#systemtexts). Widgets can define their own or use existing texts.
* The **Query Filter** section in the **Database Connection** document now includes a search option, making it easier to quickly find and select relevant filter fields.
* Maia can now generate Task Queues.
-* You can now use Maia to create and update translations in your app.
### Improvements
diff --git a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-business-event-entities.png b/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-business-event-entities.png
deleted file mode 100644
index d607761a84e..00000000000
Binary files a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-business-event-entities.png and /dev/null differ
diff --git a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-business-event-service.png b/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-business-event-service.png
deleted file mode 100644
index 07621e40bb9..00000000000
Binary files a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-business-event-service.png and /dev/null differ
diff --git a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-domain-model.png b/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-domain-model.png
deleted file mode 100644
index 4fd43616974..00000000000
Binary files a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-domain-model.png and /dev/null differ
diff --git a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-handle-cancel-task.png b/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-handle-cancel-task.png
deleted file mode 100644
index 1829da65ee2..00000000000
Binary files a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-handle-cancel-task.png and /dev/null differ
diff --git a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-handle-submit-task.png b/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-handle-submit-task.png
deleted file mode 100644
index 1de79f3d7c8..00000000000
Binary files a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-handle-submit-task.png and /dev/null differ
diff --git a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-handle-task-accepted.png b/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-handle-task-accepted.png
deleted file mode 100644
index 738142bda68..00000000000
Binary files a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-handle-task-accepted.png and /dev/null differ
diff --git a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-handle-task-completed.png b/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-handle-task-completed.png
deleted file mode 100644
index cfc9888dd26..00000000000
Binary files a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-handle-task-completed.png and /dev/null differ
diff --git a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-sub-handle-command.png b/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-sub-handle-command.png
deleted file mode 100644
index 6e12a2fbc85..00000000000
Binary files a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/adapter-sub-handle-command.png and /dev/null differ
diff --git a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/architecture-layers.png b/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/architecture-layers.png
deleted file mode 100644
index 4b06aa215f6..00000000000
Binary files a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/architecture-layers.png and /dev/null differ
diff --git a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/cleanup-processed-messages.png b/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/cleanup-processed-messages.png
deleted file mode 100644
index 0feeab9fb3f..00000000000
Binary files a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/cleanup-processed-messages.png and /dev/null differ
diff --git a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-business-event-entities.png b/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-business-event-entities.png
deleted file mode 100644
index 74021e53538..00000000000
Binary files a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-business-event-entities.png and /dev/null differ
diff --git a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-business-event-service.png b/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-business-event-service.png
deleted file mode 100644
index 3e06aa6dec2..00000000000
Binary files a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-business-event-service.png and /dev/null differ
diff --git a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-domain-model.png b/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-domain-model.png
deleted file mode 100644
index e9fb4078d9c..00000000000
Binary files a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-domain-model.png and /dev/null differ
diff --git a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-handle-cancel-task.png b/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-handle-cancel-task.png
deleted file mode 100644
index dfe5fd77a0f..00000000000
Binary files a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-handle-cancel-task.png and /dev/null differ
diff --git a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-handle-submit-task.png b/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-handle-submit-task.png
deleted file mode 100644
index 97626b2e370..00000000000
Binary files a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-handle-submit-task.png and /dev/null differ
diff --git a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-handle-task-accepted.png b/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-handle-task-accepted.png
deleted file mode 100644
index 2df3a46e75e..00000000000
Binary files a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-handle-task-accepted.png and /dev/null differ
diff --git a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-handle-task-completed.png b/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-handle-task-completed.png
deleted file mode 100644
index 78f529ff9e8..00000000000
Binary files a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-handle-task-completed.png and /dev/null differ
diff --git a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-parent-workflow.png b/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-parent-workflow.png
deleted file mode 100644
index 0f3ee8b6083..00000000000
Binary files a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-parent-workflow.png and /dev/null differ
diff --git a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-sub-handle-event.png b/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-sub-handle-event.png
deleted file mode 100644
index 925060b2a11..00000000000
Binary files a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-sub-handle-event.png and /dev/null differ
diff --git a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-task-workflow.png b/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-task-workflow.png
deleted file mode 100644
index 3e5f8b6f709..00000000000
Binary files a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/domain-app-task-workflow.png and /dev/null differ
diff --git a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/long-running-task-flow.png b/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/long-running-task-flow.png
deleted file mode 100644
index 93346acf27d..00000000000
Binary files a/static/attachments/refguide/modeling/integration/use-platform-supported-content/async-job-orchestration/long-running-task-flow.png and /dev/null differ