SAS-1810: tech ref agent editor#10980
SAS-1810: tech ref agent editor#10980tswarmerdam-mx wants to merge 21 commits intomendix:developmentfrom
Conversation
| * The app model has no consistency errors in Studio Pro (as shown in the **Errors** pane). | ||
| * The app is running locally. | ||
| * The text generation resource configured in the Model document is reachable. | ||
| * Values are provided for all placeholders so a concrete test case can be constructed. |
There was a problem hiding this comment.
should we add something about the ASU?
| ### MCP tools cannot be listed or called | ||
| If **List tools** fails, verify the consumed MCP service configuration: endpoint constant value, protocol version, and credentials microflow (when authentication is required). If possible, also confirm that the target endpoint is reachable from the running app runtime, for example by temporarily configuring it manually in the [MCP Client module](/appstore/modules/genai/mcp-modules/mcp-client/). |
There was a problem hiding this comment.
should we also point them to log files or developer tools to get more insights?
There was a problem hiding this comment.
@tinaengel-mx I included some extra lines, please check
|
|
||
| ## Installation {#installation} | ||
|
|
||
| If you are starting from a blank app or adding agent-editing functionality to an existing project, you need to manually install the [Agent Editor](https://marketplace.mendix.com/link/component/257918) package from the Mendix Marketplace. After download, you might see a warning asking for permission to add an extension to your app. Make sure to click `Trust module and enable extension` in the popup for the agent editor to be installed. |
There was a problem hiding this comment.
Do we need a similar note about private constant value permissions? And maybe something in troubleshooting if they did not give permission in the first place?
There was a problem hiding this comment.
Can you add that according to the order and texts that are shown when reviewing the typescript? I havent' gone through that flow yet. For troubleshooting I don't think we need it, because it's a design time thing only and there are banners for that
There was a problem hiding this comment.
Let's keep it out, since we have banners and developers can chnage permissions later.
…into agent-editor
4 participants
No description provided.