Basic Information

appmixer.ai.mistral.AIAgent

AI Agent

1.0.0

Public

Build an AI agent on a Mistral model that answers with context and acts through tools. Connect a component to the 'tools' output port to let the agent call it as a tool, and mark the fields the model should fill with the 'Model Defined Parameter' variable; components connected behind it run as further steps of the same tool. For a tool with its own description and logic (branches, loops), connect a 'Tool Start' to the 'tools' port and end every branch with 'Tool Output'. An MCP server on the 'tools' port gives the agent all of its tools.

Properties

FieldTypeDescription
Stream Responses toggle Stream partial responses as they arrive from the model. This only has an effect on the built-in chat utility; the agent still sends the complete answer to its output. For streaming to work, the 'Thread ID' of the agent must be set to the 'Thread ID' output of the 'Chat Trigger' component.

Input Ports

in

FieldTypeDescription
Model text Insert a model ID or select one that supports function calling, for example mistral-medium-latest. Defaults to mistral-medium-latest when left empty.
Instructions textarea The system instructions the agent follows, for example 'You are a support agent. Look the order up with the tools before you answer.'. The maximum length is 256,000 characters.
Prompt textarea The message the agent responds to.
Thread ID text Set a thread ID to keep the context of the conversation: every message with the same ID continues the same thread. Without a thread ID the agent has no memory, which suits a simple question-and-answer step.
File filepicker An optional file the agent uses as additional context. PNG, JPEG, GIF and WEBP images go to the model directly (use a vision model), a PDF is read with Mistral OCR first, and other files are sent as text, which suits CSV, JSON or source code.
Memory Data Store text A data store that keeps the conversation history, so the context survives across executions and other flows can read or export it. Without it the history is kept in the component state.

Output Ports

out

FieldTypeDescription
Answer string -
Prompt string -
Time (ms) integer -
Usage object -

tools

FieldTypeDescription
Prompt string -
Model Defined Parameter string -

Full Metadata