Choose the agent

Every conversation happens with an Agent. The selector sits at the top of the screen, next to the current Agent's name, and lists what is published in the workspace.

Agents and SuperAgents show up together, with no visual distinction. The difference between them is in how they are built, not in how they are used.

Switch agents

Open the selector and use Filter agents when the list is long. The choice applies to the conversation in progress.

Names and descriptions come from whoever built the Agent. When they are vague, the information panel usually explains better than the name.

The information panel

The Chat info button, in the header, opens a side panel with two tabs at the top: Agent and Chat.

Inside Agent, three tabs show how it is put together:

General: description, model, provider in use and when the Agent was created.
Collections: which knowledge bases it looks up, with each one's details.
MCPs: which tools it can call.

It is the fastest way to answer "why doesn't this agent know this" before opening a ticket: if the Collections tab is empty, it doesn't look up any document.

What the agent reaches

An Agent only sees what was attached to it in Admin. Nothing you write in the conversation changes that.

If the answer you need depends on a document that isn't in any of that Agent's Collections, there is no way to ask it to look it up. The way forward is to talk to whoever administers the workspace.

The Collections tab also shows each base's connectors. A Collection fed by a connector may be outdated if the sync failed, even if it shows as attached here.

When the list is empty

No Agent in the selector means the workspace has no published Agent. Drafts exist only in Admin and don't show up here.

Also check the workspace selected at the top of the sidebar: each workspace has its own Agents.

Next steps

Understand the difference between the two kinds in Agents and SuperAgents.
See how the Agent uses Collections in References and sources.