You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/marketplace/genai/how-to/create-single-agent.md
+15-4Lines changed: 15 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,10 +23,11 @@ The type of agent you can build is a single-turn agent, which means that:
23
23
* It focuses on specific task completion.
24
24
* It uses a knowledge base and function calling to retrieve data or perform actions.
25
25
26
-
This document covers two approaches to defining an agent for your Mendix app. Both approaches leverage the capabilities of Mendix' Agents Kit:
26
+
This document covers three approaches to defining an agent for your Mendix app. Both approaches leverage the capabilities of Mendix' Agents Kit:
27
27
28
-
* The first approach uses the [Agent Builder UI to define agents](#define-agent-commons) at runtime by the principles of Agent Commons. It enables versioning, development iteration and refinement at runtime, separate from the traditional app logic development cycle.
29
-
* The second approach [defines the agent programmatically](#define-genai-commons) using the building blocks of GenAI Commons, and is more useful for very specific use cases and when the agent needs to be part of the code repository of the app.
28
+
* The first approach uses the [Agent Editor in Studio Pro](#define-agent-editor). It is used for creating and iterating on agent definitions as part of the app model, leveraging existing development capabilities of the platform to define, manage and deploy agents as part of a Mendix app.
29
+
* The second approach uses the [Agent Builder UI to define agents](#define-agent-commons) at runtime by the principles of Agent Commons. It enables versioning, development iteration and refinement at runtime, separate from the traditional app logic development cycle.
30
+
* The third approach [defines the agent programmatically](#define-genai-commons) using the building blocks of GenAI Commons, and is more useful for very specific use cases and when the agent needs to be part of the code repository of the app.
30
31
31
32
### Prerequisites {#prerequisites}
32
33
@@ -214,9 +215,19 @@ To get started:
214
215
215
216
This method provides greater flexibility in managing and sharing functions across different applications and environments.
216
217
218
+
219
+
## Define the Agent Using the Agent Editor {#define-agent-editor}
220
+
221
+
The main approach to create and manage agents makes use of the [Agent Editor](https://marketplace.mendix.com/link/component/257918) in Studio Pro. This extension allows you to define, manage and deploy agents as part of your app model. With the extension you can define Agents as documents of type "Agent" in your app while working in Studio Pro, alongside related documents such as Large Language Models, Knowledge bases and Consumed MCP services.
222
+
223
+
{{% alert color="info" %}}
224
+
The Agent Editor will become available shortly after the Mendix Studio Pro 11.9 release as a downloadable extension on the Mendix Marketplace. Click 'Add to Saved' on the [Marketplace listing](https://marketplace.mendix.com/link/component/257918) and stay tuned for updates!
225
+
{{% /alert %}}
226
+
227
+
217
228
## Define the Agent Using Agent Commons {#define-agent-commons}
218
229
219
-
The main approach to set up the agent and build logic to generate responses is based on the logic part of the Agent Commons module. Start by defining an agent with a prompt at runtime, then, through the same UI, add tools, (microflows as functions) and knowledge bases to the agent version.
230
+
The main alternative approach to set up the agent and build logic to generate responses is based on the logic part of the Agent Commons module. Start by defining an agent with a prompt at runtime, then, through the same UI, add tools, (microflows as functions) and knowledge bases to the agent version.
0 commit comments