Skip to content

Teams

A team groups agents and resources around a domain responsibility. One persona can declare several teams. A team owns the goals started inside it, the agents available for those goals, and shared definitions such as boards and lists.

A Studio team lives in assets/studio-teams.json under teams. Its id is the reference used by its resources and team-scoped playbooks. Use goal for the team’s purpose. Canvas placements use bots, edges use connections, and budget declares daily and per-episode limits. Work goals, individual attempts, and approvals are created inside an installed team.

Field Meaning
revision Revision used for team definition changes
bots[].playbookId Registered executable for the placement
connections Permitted delegation, accepted-result handoff, or context-page association
automationPolicies Candidate definitions for recurring work, subject to local enablement and limits

This is a valid Studio team definition. Add it to teams. The zero budgets intentionally describe a team that needs budget setup before running work.

{
"id": "accountants",
"name": "Accountants",
"goal": "Find accounting firms and prepare evidence-backed outreach.",
"revision": 1,
"budget": { "dailyCredits": 0, "episodeCredits": 0 },
"apps": [],
"automationPolicies": [],
"bots": [],
"connections": []
}

Create the empty team, then use Quick Start → Add manually to open Add bot on Canvas. Author a playbook or install a package there. Bind its resources and check the team’s spending limit. In Work, create a goal and verify that the plan selects the intended placements and handoffs. A team with a research and writing placement can run a research-only goal without scheduling a draft.

See agent placements, goal planning, and team packages.