Agents and SuperAgents

An Agent is the unit people talk to in Chat. It brings together an AI model, written instructions and access to the workspace's knowledge and tools.

Agents belong to a workspace and are created in Admin. Nothing in Chat creates an Agent.

What an Agent is made of

The creation form organizes the Agent into sections, and each one answers a different question:

• Basic details: name, model, logo and description. The name and description are what people read when choosing the Agent.
• User response prompt: the standing instructions. It defines the tone, format and limits of what the Agent should answer.
• Collections: the knowledge it looks up before answering.
• MCPs and Integrations: the tools it can call.
• Sub-agents: other Agents it calls for support.
• Advanced options: temperature and maximum tokens per answer.

Only the name, model and prompt are required. An Agent with no collections and no tools is valid: it answers with the model and the prompt, like a plain chat.

Draft and published

Every Agent has two states. A draft exists only in Admin; a published Agent shows up in the Chat Agent selector for the people in the workspace.

You choose between them when you save, with the Publish on save option. An Agent that is created but not published stays out of sight of platform users, which is useful while you are still tuning the prompt.

How the Agent answers

For each message, the Agent builds its answer in this order:

1. If it has Collections attached, it searches them for relevant passages.
2. If it has MCPs or Integrations, it decides whether it needs to call a tool, within the configured iteration limit.
3. It combines everything with the prompt and the conversation history and asks the model for the answer.

Without attached Collections, step 1 doesn't happen, and the platform doesn't even query the search engine. Attaching Collections is what turns on RAG, not a separate switch.

Sub-agents

An Agent can expose itself as a tool and call other Agents for support. The main Agent is still the one talking to the person; the sub-agents work behind the scenes.

This is useful for splitting responsibilities, such as one Agent that knows the HR policy and another that knows the product catalog, instead of bloating a single prompt.

SuperAgents

A SuperAgent is an agent that already exists outside AUMO and that the organization registers by URL. The platform treats it as an endpoint compatible with the Responses API.

The differences that matter:

• Where it comes from: an Agent is built inside AUMO; a SuperAgent is registered by pointing to an external system.
• Who registers it: SuperAgents go into the Organization catalog and are then made available to each workspace.
• What you configure: for a SuperAgent you provide a name and an endpoint. The prompt, model and knowledge are the responsibility of whoever runs the service on the other side.

Next steps

• Understand the knowledge that feeds the Agent in Collections and knowledge.
• See where the available models come from in Providers and models.
• Build an Agent from scratch in Your first agent.