Squad — a maestro coordinates the team of agents for you
You give the brief. The maestro splits the request, holds each agent accountable, and merges the results. Copy-paste between windows is dead.
The maestro that coordinates without you copying and pasting
A squad is a named preset of coordinated agents. When you start a squad mission, exactly one pane opens: the maestro's. It reads your brief, splits the work across the agents on the roster — each invoked by name, on demand — tracks every delivery, and merges the results at the end.
The mechanism is honest by construction: the maestro (the orchestrator, in technical terms) runs without editing or shell tools. It can't do the task itself — only delegate, observe, and consolidate. And when an agent finishes, the handoff wakes the maestro instantly: event-driven coordination, not waiting.
How to use it
Start a squad
pick the preset in the mission wizard. Only the maestro's pane opens; the team is born as it's called.
Give the brief
the maestro splits the work: each agent gets its task and shows up in a visible pane on the grid.
Get the delivery
each agent reports via handoff, the maestro consolidates and synthesizes. Tokens and cost for the whole squad, aggregated in its pane.
Area chiefs and cron
In Agentic mode, command gains a second level: area chiefs — 4 types (scout, builder, reviewer, and controller) that break down the work in their area and dispatch visible agents. The chief is born on first invocation and reused while it's alive. The details of who invokes whom are in /features/missions.
And the squad doesn't need you awake: cron tools schedule recurring execution — a prompt or a skill running in a pane on an interval expression, with create, list, and remove.
What this area has today
Canonical orchestratorshipped
The maestro runs without editing or shell tools — the delegation gate forces it to delegate, never execute the task itself.
Event-driven handoffshipped
An agent finishes and reports via handoff — the maestro wakes up instantly, no polling, no phantom waiting.
Team on demandshipped
Only the maestro's pane opens at the start. Every agent on the team is born when invoked — and closes itself 30s after delivering.
Area chiefsshipped
4 chief types — scout, builder, reviewer, controller — as a second level of command in Agentic mode.
Tasks sidebarshipped
The mission milestones agents create become a visible scoreboard on the side — to do, in progress, done.
Cron / schedulingshipped
Recurring execution of a prompt or skill in a pane, on an interval expression — create, list, remove.
Overclock Originalsshipped
Builtin squads with curated composition — ready to run, updated automatically on every boot.
Aggregated squad costshipped
The maestro's pane sums tokens and cost across every pane in the mission — including the ones that already closed.
Status straight from the product's brain: shipped = actually in use; partial = exists, with documented limits.
Where this actually gets to work
all squads →App Factory
Backend e frontend em paralelo, contra o contrato — não um contra o outro. App web com dados seed pra você usar no primeiro clique: pico de 8+ panes, 3 gates.
Overclock OriginalCinema Site
Rouba o DNA da referência. Entrega uma produção de cinema: site completo com design extraído ao vivo, copy por seção e 6 imagens geradas em paralelo — pico de 9 panes, 2 gates.
Overclock OriginalSaaS 10K
O app inteiro do App Factory. E de cima, o cofre: 4 auditores simultâneos interrogam auth, dados entre tenants e billing — pico de 12+ panes, gates do Factory +2.