Why a Team
A team of specialized Agents is better suited to complex tasks that span different business domains, for the following reasons:- Focused context: an Agent with too many responsibilities pulls in a lot of irrelevant context, which hurts quality and drives up token cost. Split by domain, each Agent keeps its context focused, answers more accurately, and costs less.
- Complementary capabilities: each Agent can be bound to a different model and skill set, and through division of labor, collaboration, or even cross-review, the team can handle tasks a single Agent would struggle with.
- Data and permission isolation: each Agent has its own workspace, and its memory, sessions, and output files are not visible to others, which fits boundaries drawn by role or by customer.
- Better presentation: different channels, or different instances of the same channel, can connect to different Agents and appear as separate assistants, or an entire team can join one channel to answer collaboratively, making it easy to set up a team of digital employees.
Creating an Agent
Click Create on the “Agent Team” page in the Web console or desktop client to add an Agent. An Agent is made up of the following parts:- Name and avatar: the identity within the team, shown in chat bubbles, the member list, and channel bindings.
- Responsibilities: one sentence describing what the Agent handles. It helps you tell members apart and is used to decide who a task should go to during collaboration.
- Default model: you can assign a model to this Agent individually. The default Agent follows the global configuration.
- Skills and knowledge: these can be shared with the team, or an Agent can have its own dedicated knowledge base that stays isolated from the others.
- Copy from an existing Agent: when creating a new Agent, you can copy an existing Agent’s configuration, skills, and knowledge as a starting point.
Once created, the Agent appears in the team list. Click any member, and on the right you can switch between “Overview / Skills / Core Files” to configure its basic information, enabled skills, and its persona and rule files (AGENT.md, RULE.md, and so on).
There is always a default Agent in the team. It is the fallback for new sessions and elsewhere, follows the global model configuration, and cannot be deleted.
Knowledge Base: Shared or Independent
Every non-default Agent can choose a knowledge base mode:- Shared: reads and writes the same knowledge base as the team, which fits scenarios where everyone works with the same materials.
- Independent: has a dedicated knowledge base isolated from other members, which fits cases where materials differ significantly across domains.
Joining Sessions and Group Chats
When creating a session, you can have a single Agent talk with you, or start a group chat with multiple Agents. In an existing session, the Agent selector at the bottom left of the input box lets you:- Switch Agent: an empty session can switch its Agent directly; a session that already has content starts a new conversation with the new Agent, while the existing history stays with the original Agent.
- Add member: add another Agent to the current session, turning it into a group chat.
- Remove member: remove a member from the current session.
In a group chat, each Agent answers with its own configured model, and the bubble shows which Agent is speaking. Members in the same session read the same record and can see what others have said.
Group chats do not use the session-level model selection; each Agent uses its own configured default model, so no model selector appears in a group chat.
Channel Integration
A channel of the same type can run multiple instances, and each instance can be bound to a different single Agent or Agent team, appearing as its own separate assistant. On the “Channels” page, set the bound Agent for a connected instance:- The first one selected is the owner, responsible for receiving all tasks from this channel.
- You can add more members, and the owner assigns suitable tasks to them based on their responsibilities.
- In the channel, use
@followed by a member’s name or ID to talk to that member directly.
Binding changes take effect immediately, with no need to restart the channel. Channels that support multiple instances include WeChat, WeCom bots, DingTalk, Feishu, QQ, Telegram, Slack, Discord, and more.
Collaboration
Multiple Agents in the same session collaborate in two ways.1. Directing with @
In a group chat, use@ followed by a member’s name to hand the current turn to a specific Agent. Typing @ brings up the members in the current session to choose from, and once sent, the bubble carries the avatar of the directed Agent to mark who is responsible for that turn.
2. Lead Agent and Delegation
A group chat always has a lead Agent (the owner). Unless the user@s someone else, it receives every task. Delegation lets the lead Agent hand a task outside its own domain to a more suitable member:
- Decide: after receiving a task, the lead Agent decides automatically, answering directly if the task is within its domain and forwarding it to a more suitable member in the session otherwise.
- Execute: the delegated member completes the task in its own workspace and returns the result to the lead Agent.
- Reply: the lead Agent consolidates the results and replies to the user, who always faces a single entry point.
Differences from Sub-Agents
Agent teams and sub-Agents both share the workload, but they serve different purposes:In short: use team collaboration when the task itself belongs to another persistent Agent (one that holds the relevant knowledge, permissions, or customer relationship); use a sub-Agent when you just want to split your own task to run in parallel and speed things up.