Groups and teams

Make a group#

• Select two or more consoles and press ⌘G. The group is named Group 1, Group 2 and so on. ⌘ShiftG dissolves it.
• Drag a console into a group's halo to add it, or out of the halo to take it out.
• By command: make a group of three Claude Code agents, add two testers to group 2, group the testers.

Launch a team with the composer#

Spawn 4 and Group in the command bar, and Spawn group in the right-click ring, open the composer:

• A group name and a role: General, Frontend, Backend, Testers, Reviewers, Design, Docs or Security. The role names and tints the group; it does not change what the agents can do.
• One slot per console, up to 12. Click a slot to cycle its agent, right-click it for the whole catalog, or pick a logo in the fill-all row to set every slot at once.
• Spawn launches them together.

Roles and the agent they start#

When you ask for a role without naming a CLI, Symvibe picks one: reviewers, frontend, design and docs start Claude Code; backend and security start Codex; testers start Gemini. A general request with no CLI and no role, such as spawn two agents, opens plain shells. Name the CLI to choose: spawn two codex reviewers. Consoles added to an existing group without a named CLI, as in add two testers to group 2, start your default agent instead.

Give a group work#

• Mention it, @Reviewers, or name it: tell group 2 to write tests for the cart.
• Work for a group is split among its members or given to the first free one, as How orders reach your agents explains.
• Pause, resume, restart or kill a group by name. Restarting and killing ask first.

Team reports#

Each member's reply lands in the thread the order came from, the command bar's or an orchestrator card's, when it finishes or fails. Symvibe knows a member finished from live agent status when it is on, and otherwise from its output going quiet. Ask who finished or give me a summary, or forward the results to the next agent with a forward.

Keep going#