Human vs Agent Responsibilities

This page is the operating contract for Metateam.

If you remember one rule, remember this: humans drive intent in the dashboard; agents run most CLI commands in their own terminals.

Responsibility Split

Surface Human responsibility Agent responsibility
Terminal dashboard (metateam) State intent, monitor progress, intervene, approve/reject direction Execute tasks, coordinate with peers, report results
Web interface (metateam.ai) Review sessions, manage KB content, manage account settings/keys N/A
CLI in agent terminals Rare human recovery only Primary execution surface (crew, kb, memory, repo, etc.)

Human-Primary Shell Commands

Use these directly when needed:

  • metateam (launch dashboard)
  • metateam setup (first-time setup)
  • metateam account register
  • metateam account login
  • metateam account whoami
  • metateam session search [QUERY] (diagnostics/verification)

Dashboard Controls Humans Actually Use

From current dashboard keybindings:

Key Action
F1..F9 Jump to crew member tab
F10 / F11 Previous / next tab
F12 Open/close help and command mode
F12, a Summon agent dialog
F12, m Message composer
F12, / Slash command panel
F12, c Communication log panel
F12, Enter Attach directly to tmux session
F12, p Silence crew messages for 1 minute
F12, w Toggle watchdog
F12, o Settings
F12, q Quit dashboard (agents keep running)
F12, Esc Send Esc to all crew tabs

Slash Commands in the Dashboard Message Overlay

  • /msg <target> <text>
  • /broadcast <text>
  • /summon <target>
  • /release <target>
  • /screen <target>
  • /reset <target>
  • /crew
  • /personas
  • /kb <query>

Agent-Primary CLI Surface

These are usually executed by agents, not typed by humans during normal operation:

  • metateam crew message|summon|release|screen|reset|inbox
  • metateam kb ...
  • metateam memory ...
  • metateam repo ...

Escalation Path for Humans

  1. Try the dashboard first (metateam + F12 actions).
  2. Ask the leader persona (for example Data) to perform command-level actions.
  3. Use direct CLI only for setup, auth, or diagnostics.