Your team
By the end of this page your system will have a team of agents the planner can build plans from.
Prerequisites
- A Planner / Executor system open in the editor (Editor tour).
- Two or more Active AI Agents in the project, each with skills.
- Admin or Developer role.
What the team is
The team is a flat pool of agents the planner is allowed to use. You do not connect them to each other and you do not order them — the plan supplies both, fresh for every turn.
The Configuration panel opens with Your team at the top, showing how many agents you have and a Manage members link. The same catalog is what the centre List view shows.
Add agents
Open the member list
Click Manage members in the Your team group, or use the Add agent button above the member list.
Pick the agents
Choose from your project’s AI Agents. Only Active agents can be members. Task Agents are not offered — expose one as a tool on a member agent instead.
A team for research-and-publish work might hold Sales Analyst, Market Researcher, Content Writer, Fact Checker and Editorial Reviewer. The planner picks whichever of them a given request needs — a numbers question uses one, a launch email uses four.
Save
Click Save in the header. Members are part of the system’s configuration, so they only reach the preview once saved.
How the planner chooses
The planner reads each member’s skills — their names, descriptions and example queries — and picks the ones a goal needs. It never sees anything you write in the system’s own description.
That makes skill quality the main thing under your control:
| Symptom | Usual cause |
|---|---|
| An agent is never chosen | Its skills are vague, or describe the same ground as another member’s |
| The wrong agent runs a step | Two members’ skills overlap; the planner picked either one |
| A plan has more steps than the job needs | Members are split too finely — one agent could cover several steps |
Before adding an agent to a team, open it and read its skills as though you were the planner. If you cannot tell from the description alone what the agent is for, neither can the planner. See Skills.
How many members
- A system with no members cannot run a turn. The panel says so, and the preview will not produce an answer.
- With one member, the planner can only ever produce a single-agent plan. The editor warns you about this — it is valid, but a single AI Agent would do the same job with less machinery.
- Two or more is where the pattern starts earning its cost.
Removing a member
Remove an agent from the member list and save. Nothing else needs changing: the next plan is written against the team that remains.
This is the practical difference from an Agent Graph, where removing an agent leaves a hole in the drawn flow that you have to repair.
Common issues
- An agent is missing from the picker — It is not Active, or it is a Task Agent.
- “A system with an empty catalog cannot run a turn” — Add at least one member.
- “With one member the planner can only ever produce a single-agent plan” — A warning, not an error. Add a second member, or use a single AI Agent instead.
- A new member is ignored in the preview — You have not saved since adding it.