Squads

A Squad is an optional multi-assistant collaboration mode. Day-to-day 1:1 usually uses Mesh: an assistant can ask roster peers for help without forming a team first.

Create a Squad

Sidebar + → Create squad, pick member assistants, set name and description. The squad avatar stitches member avatars.

How it works

You send one task to the squad. The captain breaks work down and dispatches; members speak or call tools as needed. Member bubbles show their avatars. A squad can also keep its own schedules, long-running task checklist, and resources library (see Evolution, Assistants).

Mesh (1:1 peer help)

In a normal assistant session, the model can ask another assistant for help (ask_assistant); the UI shows status lines and a read-only transcript. The roster exposes peer names and descriptions (not SOUL / skills / memory bodies).

• Nested asks have no separate depth cap; assistants already on the call chain cannot be asked again (loop guard).
• Nested runs use the same max-turn limit as 1:1.
• The main chat does not show ask/reply bubbles; status lines and the read-only panel show the exchange.

Approvals and restore

Member tool approvals do not overwrite each other. After restart, a squad can cold-restore unfinished approval turns; the captain continues the round with member results and does not re-dispatch the same subtask. Captain checkpoints can also be silently resumed by the global Watchdog (except after manual Stop, pending HITL, or in-flight soft-steer).

When to use

• Clear multi-role parallel flows (e.g. write + review + docs)
• Research + summarize + translate

For a quick second opinion, use Mesh; create a Squad when you need captain orchestration across roles.