Skip to main content
AgentTeam coordinates multiple agents working together, executing tasks sequentially or in parallel.
AgentTeam replaces Agents and PraisonAIAgents as the recommended class name. The old names still work as silent aliases.
Seven team-level options are now honoured — memory, context, hooks, execution, planning, managerLlm, and runOn (which is refused with a TypeError, matching Python). Eight more (knowledge, guardrails, web, reflection, caching, learn, autonomy, toolsRunOn) are accepted for Python-SDK parity but emit a [praisonai] … not yet honoured notice. See the Parity Notices page for the full list.
Most Python AgentTeam.* helper methods are not yet on Team in TypeScript. Drive a team with start() and the options above; see the SDK parity baseline for the current method list.

Quick Start

1

Simple Usage

2

With Configuration


How It Works


Configuration Options


Team-Level Options

Seven options now shape how the whole team runs.
One shared store for the team — recalled entries are appended to each task’s prompt as bullet lines, and each task’s result is written back.
Recalled entries are appended as bullet lines (• text) with no section header. Each completed task is written back as a user + assistant turn with { task, userId } metadata; userId defaults to "praison".

Hierarchical Process

With process: 'hierarchical', a Manager agent decides task order and delegation. The manager is built under the hood on managerLlm and replies with pinned JSON:
action is "execute" | "stop". On a parse error the whole run breaks and no member task runs (Python parity). Outcomes (HierarchicalOutcome): 'completed', 'stopped', 'max-iterations', 'invalid-selections', 'manager-error'. Results always come back in task order regardless of the order the manager delegated.

Read-Only Accessors

After start(), inspect what the team assembled.

How the Retry Loop Works

completionChecker returning false triggers a retry, bounded by execution.maxRetries. The default completionChecker accepts any non-empty answer. On final failure the task is marked { status: 'failed' } — the task still ends and the run continues. This is the same rule as Python.

Common Patterns


Best Practices

When agents need context from previous agents, use sequential mode.
When tasks are independent, parallel mode is faster.
Provide one task per agent for explicit control.

Backward Compatibility

All old names work as silent aliases with no deprecation warnings.

Agent

Single agent documentation

AgentFlow

Step-based workflows

AgentOS

Deploy as web service