Why Mobs Exist
Single sessions are excellent for linear work. Mobs are for work that benefits from separate participants:- one lead plus several analysts
- independent reviewers that compare findings
- long-lived helper pools
- incident rooms with specialized roles
- browser-deployed teams packaged as mobpacks
The Objects
Stable Identity
Public mob APIs useAgentIdentity. Runtime bindings can rotate when a member
respawns, moves, or reconnects, but the member’s public identity remains the key
for status, wiring, work, and events.
lead-1 to analyst-1 instead of wiring internal
session IDs.
Host Vs Agent Surfaces
Mobs deliberately expose two kinds of interfaces:
Agent tools let an agent create or coordinate helpers while it is working. Host
APIs let applications create, supervise, inspect, and drive teams directly.
Runtime Modes
autonomous_host is the default when a member’s runtime mode is omitted. The
member behaves like a long-lived peer and receives work through the mob runtime.
turn_driven is explicit. Use it when the host wants tighter control over when
the member starts turns.
Flows And Work
Flows are repeatable workflows over members. Work lanes are tracked, cancellable pieces of work sent to a mob or member. Use a flow when the workflow itself is reusable; use work submission when an application needs a handle for one unit of work.Portability
Mobpacks package a mob definition and optional assets into a.mobpack file.
They are the portable deployment shape for signed teams, repeatable CLI/service
deployment, and browser-target builds.
See Also
Mobs guide
Build, spawn, wire, run flows, observe, and troubleshoot mobs.
Mob architecture
Runtime ownership, identity, persistence, and flow internals.
Mobpack
Package and deploy portable mob artifacts.