What the Team editor is
The Team editor is the main operating surface for a scaffolded team. If Recipes is where teams get created, the Team editor is where they become understandable and manageable.What you can manage there
A team page typically exposes tabs for:- Recipe
- Agents
- Skills
- Cron
- Files
- Orchestrator
- Memory
- Workflows
What each area is for
Recipe
Use this when you want to understand or evolve the team definition itself. A practical use case is turning an installed team into a custom editable recipe instead of continuing to rely on a bundled default.Agents
Shows the agents or roles that make up the team and lets you inspect or navigate into them.Skills
Use this to see or install team-relevant skills that should be available across the team workspace.Cron
This is where scheduled behavior becomes visible and manageable for the team.Files
One of the most important tabs in the whole product. The system is file-first, so direct visibility into team files is a major part of understanding what the team is actually doing.Orchestrator
Advanced operational visibility for swarm/orchestrator setups.Memory
A place to inspect memory-related artifacts and conventions tied to the team.Workflows
Where the team’s workflow definitions live and where you branch into workflow editing and run inspection.
Practical example
A common real-world loop looks like this:- scaffold a development team from a recipe
- open the team in ClawKitchen
- inspect files and roles
- verify cron behavior
- inspect workflows
- make adjustments to the recipe or the team files as needed