Team Configurations

Teams let you save and restore entire agent setups. Instead of spawning agents one by one, define a team once and load it whenever you need that configuration.

Saving a Team

Once you have a set of agents running the way you want, save them as a named team:

groove team save my-fullstack

This captures every active agent's role, scope, provider, model, and permission settings. The configuration is stored locally in .groove/teams/.

From the GUI, use the Team Selector dropdown in the header to save the current setup.

Loading a Team

Loading a team spawns all saved agents with their original configuration:

groove team load my-fullstack

All agents launch in parallel with the correct roles, scopes, and models. The introduction protocol runs for each one, so they are immediately aware of each other.

Quick Workflow

Save a team after your first setup session. From then on, groove team load my-fullstack gets you to a full working state in seconds.

Built-In Templates

Groove ships with three starter templates:

Template	Agents	Use Case
fullstack	Backend + Frontend + Testing	Full-stack web development
api-builder	Backend + Testing + Docs	API development
monorepo	Multiple Backend + Testing + Planner	Multi-package repositories

groove team load fullstack

Export and Import

Share team configurations with your coworkers or across machines:

Export

groove team export my-fullstack

This outputs the team as a JSON file that can be shared, committed to a repo, or transferred to another machine.

Import

groove team import ./my-fullstack.json

Imports the team configuration and makes it available for loading. The JSON format is an array of agent configurations with role, scope, provider, and model for each agent.

Managing Teams

List all saved teams:

groove team list

Delete a team you no longer need:

groove team delete my-fullstack

Both operations are also available from the Team Selector in the GUI header.