Skip to main content
A team is a named container with an optional description. Local team metadata and agent membership are stored separately. .polpo/teams.json:
.polpo/agents.json:
API responses materialize a Team with its agents array, but agents is not stored inside .polpo/teams.json. Likewise, teams do not belong in polpo.json.

Reporting relationships

reportsTo is an agent field. The runtime adds it to the agent’s organization prompt and can use it as escalation context. It does not automatically reassign every failed task or delegate work. Deterministic escalation is configured on the task’s retryPolicy with fallbackAgent, escalateAfter, and optional escalateModel.

API

Team routes are nested under the Agents resource:
Use the Agent API to add or update members and select their team.

Mission-scoped agents

Temporary agents are defined as an array in a mission document’s team field. The mission executor marks them volatile, associates them with the execution group, and cleans them up according to volatileCleanup. They are not permanent project-team definitions. See Missions.