Agent Editor

Content Type: Module
Categories: Extensions,Artificial Intelligence

Overview

The Agent Editor module enables users to develop, test, optimize and ship agents as part of their app lifecycle in Studio Pro.

 

The initial release provides the following features:

  • Agent-specific Studio Pro documents for agent definitions and related dependencies, including text generation models, knowledge bases, and consumed MCP services.
  • Prompt authoring with placeholder support, so runtime values from user or context objects can be injected during execution.
  • Tool and knowledge base configuration directly in the Agent editor, including activation toggles for fast iteration and comparison.
  • Built-in local test functionality from Studio Pro to validate prompts and agent behavior before release.
  • Microflow integration through the 'Call Agent' toolbox action under the 'Agent Editor' category.
  • Agent definitions as app-model documents under version control, making changes traceable and allowing rollback to previously committed states when needed.
  • Deployment together with the app model, with environment-specific flexibility through constant overrides.

 

Limitation

Currently, the Agent Editor only supports Mendix Cloud GenAI as a provider. Support for other providers, such as (Azure) OpenAI and Amazon Bedrock, is planned for future releases.

 

Contact Us

For support and questions, feel free to reach out via email genai-components-feedback@mendix.com or Community Slack.

Documentation

First-Time Setup

After installing the dependencies, complete the following setup before defining the model and agent documents:

 

  1. Exclude the /agenteditor folder from version control. In the Studio Pro, go to App > Show App Directory in Explorer. Then, in the file explorer, edit the .gitignore file and add /agenteditor on a new line. This folder contains log files and should typically not be tracked in Git.
  2. Ensure the encryption key is configured in the App > Settings > Configuration in Studio Pro. Make sure that it is 32 characters long. For more information, see the EncryptionKey Constant section of Encryption.
  3. Configure startup import logic. Select ASU_AgentEditor as your after-startup microflow in App > Settings > Runtime, or add it to your existing after-startup microflow.

 

For dependencies, configuration and troubleshooting, see documentation on Mendix Docs.

Releases

Version: 1.0.1
Framework Version: 11.9.1
Release Notes:

We fixed two bugs where:

- in certain cases consistency checks for the agent editor could not be finished resulting in an error

- large agent definitions would cause unexpected UI behavior

Version: 1.0.0
Framework Version: 11.9.0
Release Notes:

The Agent Editor module enables users to develop, test, optimize and ship agents as part of their app lifecycle in Studio Pro.

 

The initial release provides the following features:

  • Agent-specificStudio Pro documents for agent definitions and related dependencies, including text generation models, knowledge bases, and consumed MCP services.
  • Prompt authoring with placeholder support, so runtime values from user or context objects can be injected during execution.
  • Tool and knowledge base configuration directly in the Agent editor, including activation toggles for fast iteration and comparison.
  • Built-in local test functionality from Studio Pro to validate prompts and agent behavior before release.
  • Microflow integration through the Call Agent toolbox action under the Agent Editor category.
  • Agent definitions as app-model documents under version control, making changes traceable and allowing rollback to previously committed states when needed.
  • Deployment together with the app model, with environment-specific flexibility through constant overrides.