Start here

Overview Shipped

A run takes minutes and fans out across dozens of dispatches. There is a live progress site, a terminal stream, and a written report — you are not meant to sit and wait on a spinner.

A fanned-out run is opaque by default: dozens of concurrent dispatches, no single log that reads in order. So the run publishes its own event stream, and a static site renders it live — which specialists are running, which have finished, what each one found, and where the time went.

The progress site

The live run view: each specialist as its own lane, filling in as its pillar completes. Opens automatically when a run starts.

Three ways to follow a run

  • The progress site — opens in a browser when a run starts, updates as pillars finish, and stays afterwards as the run's permanent record.
  • The terminal — the driving session streams the same events as they happen.
  • myteams <team> log — the run's event stream after the fact, defaulting to that team's latest run. myteams sessions log <run> is the same replay addressed across every team, for when you remember the run but not which team produced it.