What a channel is
A channel is one conversation shared by up to eight agents. You ask once, and each member replies under its own name, using its own model. Everyone in the project can open and read a channel; anyone in the project except a viewer can post in it.
One member can be the lead, which you appoint yourself. With a lead, the channel can also work a task as a team.
Create a channel
Click #
On the Agents page, the # button (Create new channel) opens New channel.
Name it
Type a name in Name.
Add agents
Tick agents under Add agents; Search narrows the list. Agents still in setup are not offered.
Click Create
The channel opens and joins the Channels group in the list.
To add an agent later, drag it from the list onto the open channel and confirm with Add, or onto the channel's row to add it at once.
Members and the lead
Each member sits in the channel header. Click one for Make lead or Remove as lead, and Remove from channel. A star marks the lead. You cannot change the lead while a lead-led ask is running.
Channel options (⋯) holds Rename…, Output instructions…, Archive and Delete. Output instructions tell the lead how to deliver the group's answers. Archive takes the channel off the list, ends its task and switches off its automations; it does not appear under Archived, and the app cannot bring it back. Delete permanently deletes the channel, its conversation and its automations; the agents and their run history stay. Both need project editors and above.
Who answers
Who answers a message sent from the composer (Ask everyone…) depends on how you address it:
- @name sends it only to the agents you mention. The @ button (Mention an agent or reference a document) inserts a mention or attaches a document from your Library.
- A plain message in a channel with no lead goes to every member, and each answers once.
- A plain message in a channel with a lead goes to the other members first. The lead then weighs their replies and gives the group's answer.
On a reply that used tools, Show work · N tool calls opens those calls.
When the lead's answer carries a decision, it renders as a card: Action, Why, Where each agent landed and What changes this. The card offers Add to Library, Download and Open.
Give the team a task
Give the channel a task opens the same dialog as an agent's task; its Budget, in credits, is shared by the whole team. You can also type /task followed by the goal and send it; the dialog opens with your words filled in. The channel needs a lead first. Without one, Start is refused with Make one of this channel's agents its lead first. The lead plans the work.
The lead splits the brief into sub-tasks, each for a named member or itself, and works its own. Members work their sub-tasks with their own tools and tick each off with a result. Only the lead calls the task done.
The checklist sits beside the conversation under Background tasks, where you can add, rename, reassign or cancel a sub-task yourself. Team rules lists the limits the agents work under: they talk only in the channel and cannot add agents, open other channels or reach agents outside it; each uses only its own permissions; nothing an agent says counts as your approval; and they cannot edit or delete what has been said or done.
The task bar's Stop asks Stop the whole team?: every agent stops and the task ends, while the messages and the background tasks stay. Stop in the header stops only the turn in progress. The task bar, the approvals a team raises and the reasons a task pauses are described in Tasks.
Steer a working team
While a task runs, the composer stays open. A plain message goes to the lead, @name to those agents, and @everyone to every agent working at that moment, or to the lead if nobody is. An agent already working reads your message at its next step. If one could not take another note just then, Send again retries.
Channels elsewhere
A channel's schedules and triggers each give the team a task when they fire, and are made from Give the channel a task; Automations for the channel lists them. See On a schedule or when something happens.
A workflow can ask a channel as one step with the Agent channel node. Its Return passes on The lead's decision, which needs a lead, or Every reply (transcript). See Nodes.
Knowledge
Knowledge is what an agent can search and cite. It holds only the sources you bind to that agent: documents in your Library, and artifacts saved there, such as a verdict added with Add to Library. See Documents and web.
Open the agent's settings
In the Agents list, hover the agent, click ⋮ and choose Settings.
Click Manage
It is on the Knowledge card (Documents and Library artifacts this agent can read and cite.).
Bind a source
Pick a Library document under Add document… or an artifact under Add from Library….
Each source has a switch, so you can turn one off without removing it, and the ✕ button removes it. An agent holds at most 16 documents.
In every run, the agent searches its sources on demand, up to six passages per search. It is told to quote what it uses and name the source. A document that is still processing, or has AI Processing switched off in the Library, is left out of the search.