How to run an agent team (Штаб агентов)

This guide is the “GO” path: install the Fleet HQ pack, start a durable multi-agent job, watch it in Fleet Control / Штаб агентов, keep memory on the board, and survive a restart.

Portraits also ship in the desktop app (agent-roster/). Repo masters: docs/plans/assets/agent-roster/.

≤15-minute pack install

vibeos pack apply multiagent-memory --apply
vibeos multiagent-memory doctor
vibeos kanban template apply research --slug hq-research --switch
scripts/smoke-multiagent-memory-golden.sh   # offline G1–G12

Desktop RU UI: Штаб агентов (Agents). English: Fleet Control.

Pack surface in the app: Settings → Fleet HQ (RU: Штаб агентов) — same doctor/preset as vibeos multiagent-memory doctor / pack apply.

Choose the right launcher

Job length	Use	Survives restart?
Minutes, same chat	delegate_task	No
Hours / multi-profile	Kanban / vibeos research swarm	Yes
Recurring checks	Cron + Monitor delta gate	Yes

Rule: if you would be sad to lose the work when the app quits, put it on a board.

One-command research team

vibeos research swarm --topic "What changed in EV battery costs this year?" \
  --board ev-research --workers 2

What you get:

1. Research board template (roles + Board KB seed).
2. Kanban Swarm graph: researcher gatherers → critic gate → orchestrator synthesize.
3. Progress Ledger on the root card + a Board KB finding.
4. Concurrency cap on parallel gatherers (--workers, default 2, max 4).

Then start / keep the dispatcher (gateway with kanban.dispatch_in_gateway: true, or vibeos kanban dispatch).

Profiles named researcher, critic, and orchestrator (or matching assignees) should exist so workers can be claimed.

Watch the fleet

Open desktop Agents / Fleet Control / Штаб агентов (user guide):

• Role portraits (Orchestrator, Researcher, Critic, …).
• Kanban workers vs in-session children.
• Waiting for your OK inbox — approve/deny dangerous commands and see CAPTCHA / assignee=human board cards.
• Pause new spawns / Stop a child / promote hint for long background work.
• Today at HQ timeline — merged kanban + delegation + cron (also vibeos kanban timeline).

Operator eyeball checklist (optional): docs/ops/multiagent-memory-desktop-eyeball.md.

Monitor mode

For “wake me only when something changed”:

# See docs/ops/cron-monitor-mode.md
python cron/scripts/monitor_delta_gate.py \
  --state "$VIBEOS_HOME/cron/monitor-feeds/example.state" \
  --cmd 'curl -fsS https://example.com/status.json'

Last stdout line {"wakeAgent": false} → no LLM tokens that tick.

Human in the loop

Signal	Where you see it	What to do
Dangerous command	Fleet OK inbox / chat strip	Approve once or Deny
CAPTCHA / challenge	Fleet OK inbox + block_kind=challenge	Solve Live View, then vibeos kanban unblock <id>
Missing input	Board assignee human	Answer / unblock

Ops notes: docs/ops/challenge-gate-manual-e2e.md, docs/ops/cron-research-challenge.md.

Restart mid-swarm (G9)

Kill the gateway while a worker is running, then bring it back. Claims reclaim; Board KB and ledger stay on disk.

Full runbook: docs/ops/kanban-swarm-restart.md.

Offline check:

scripts/run_tests.sh tests/vibeos_cli/test_research_swarm_restart_g9.py -q

Event → board (no LLM)

GitHub / Cursor Automations / HTTP → durable card:

echo '{"issue":{"title":"Flaky CI"}}' | vibeos kanban from-webhook --title '{issue.title}'

Or webhook route create_kanban: true — see docs/ops/event-triggers-cursor-map.md.

Related

• Fleet Control
• Kanban
• Delegation
• Persistent Memory
• Masterplan: docs/plans/2026-07-17-multiagent-memory-masterplan.md