AgentTeam (also exported as PraisonAIAgents) applies autonomy at the team level; the feature options belong on each Agent.
execution follows the same split: pass MultiAgentExecutionConfig at the team level and the single-agent ExecutionConfig on each Agent. Passing the single-agent ExecutionConfig to the team now emits a UserWarning listing the fields it cannot map. See ExecutionConfig vs MultiAgentExecutionConfig.Quick Start
1
Put feature options on each Agent
Give every agent its own
web, knowledge, or other feature options.2
Put autonomy on the team
autonomy is the one option the team applies for you.How It Works
AgentTeam accepts six feature options for API symmetry with Agent, but does not apply them at the team level. Passing them logs a warning and ignores the value.
Common Patterns
Move the option down from the team onto each agent.Best Practices
Set feature options per role
Set feature options per role
Each agent has a different job. Give the researcher
web=True and the writer
reflection=True rather than forcing one option across the whole team.Reserve the team for autonomy
Reserve the team for autonomy
autonomy is the only feature option the team propagates. Keep team-level
configuration to autonomy, process, and manager_llm.Watch the logs
Watch the logs
A warning on construction means an option landed in the wrong place. Move it
onto the
Agent(...) instances it was meant for. Passing the single-agent
ExecutionConfig to the team warns and adapts what it can — use
MultiAgentExecutionConfig instead. See
ExecutionConfig vs MultiAgentExecutionConfig.Related
Knowledge Quick Start
Give each agent its own documents
Multi-Agent Pipelines
Coordinate multiple agents

