Chats
A chat is a conversation that produces work. Everything an agent does happens in a chat — including runs you never started by hand, so you can always read back what happened and why.
Organization chats
Open Chats and start one without picking an agent. This is a general assistant for your whole organization: it can use every active integration your organization has connected, and it can hand work to your agents.
Type @ to mention an agent and delegate to it. The agent runs in a new chat of its own, and the
result is linked back into your conversation. If the agent stops because a tool needs your
approval, you get a link straight to that chat.
Agent chats
Open an agent and start a chat with it. The agent runs with its own instructions, its enabled tools and its capabilities.
In an agent chat:
@mentions a file in the agent's storage./selects skills to load for that message.- You can attach files — up to ten per message.
Admin chats
An admin chat is a chat about an agent instead of with it: you describe the changes you want and the settings are updated for you. See admin chat.
Chats started automatically
When a trigger or schedule fires, the run gets its own chat. These appear in the agent's chat list marked with the icon of whatever started them, so automated work is as reviewable as work you asked for directly.
Models
Each chat starts on its agent's default model, and you can switch model per chat. Longer conversations are compacted automatically as they approach the model's context limit, so a chat can keep going without you managing it.
Titles and search
Chats are titled automatically from their content, and the chat list is searchable, so you can find a past run without remembering exactly when it happened.