本示例演示 TeamAgent 作为另一 TeamAgent 的成员:project_manager 委派给内层 dev_team,再由 dev_team 协调 backend_dev 与 frontend_dev,并行处理实现与文档角色。
- 两层
TeamAgent:project_manager→dev_team(仍为TeamAgent) - 内层与外层均可
share_member_interactions=True - 成员工具涵盖 API 设计、UI 设计与文档格式化等模拟能力
- 根节点:
TeamAgent(project_manager)- 成员:
TeamAgent(dev_team)- 成员:
backend_dev(LlmAgent)、frontend_dev(LlmAgent)
- 成员:
- 成员:
doc_writer(LlmAgent)
- 成员:
agent/agent.py:先构造backend_dev、frontend_dev与dev_team,再与doc_writer一并交给project_manageragent/tools.py:design_api、design_ui、format_docs等run_agent.py:多轮产品需求对话,打印跨层委派与工具调用
- Python 3.12;仓库根目录
pip install -e . - 配置
TRPC_AGENT_API_KEY、TRPC_AGENT_BASE_URL、TRPC_AGENT_MODEL_NAME
cd examples/team_member_agent_team
python3 run_agent.py[START] team_member_agent_team
...
[project_manager] Tool: delegate_to_member, Args: {'member_name': 'dev_team', ...
[dev_team] Tool: delegate_to_member, Args: {'member_name': 'backend_dev', ...
[dev_team] Tool: delegate_to_member, Args: {'member_name': 'frontend_dev', ...
...符合本示例测试要求:日志体现 project_manager → dev_team → 前后端成员的嵌套委派与工具输出,与层级设计一致。
- 大型项目需「小队套小队」时使用嵌套
TeamAgent,避免单层成员过多 - 可按职能拆分外层(产品/项目经理)与内层(开发小队)