Skip to main content
简体中文 DESIGN → Teams groups Agents into an assignable team. The Lead interprets the objective, chooses members and combines results. Members contribute specialist capabilities. Choose a Workflow for fixed ordering and branching rules.

Create a team

First verify each member with a small individual task. For a reporting team, choose a coordinator as Lead and add Researcher and Reviewer members. In Roles & members, define each role’s responsibility and output: the Researcher supplies sourced facts; the Reviewer checks evidence and uncertainty. Team Instructions define shared goals, boundaries and the final deliverable. Avoid giving every member the same broad instructions. The Lead chooses which members a request needs. Membership is an available capability set, not a promise that every member runs on every request.

Check readiness

Members can use different execution types. Before configuring Runtime policy or member overrides, check capabilities, runtime targets and security constraints. Additional candidates do not imply seamless session migration.

Try and expose the team

Assign a small Issue to the Team. Inspect discussion, Task map and execution results. Confirm that the Lead produces a combined deliverable and explains failures or missing information. Keep human acceptance for work needing review. Use Teams from Issues, Automations or job Endpoints. After editing, verify a new execution; earlier executions retain their team snapshots for traceability. Continue with Team collaboration and extension · Endpoints.