Dispatch mode

The default workflow has you paste one prompt per phase. Dispatch mode is hands-off: the Manager agent does every paste for you. It launches each phase via zyme dispatch, waits for the worker, reads the result, and advances.

Tell the Manager what to optimize. Walk away. Take a nap. Come back to a finished task.

How to start

In a fresh coding-agent session inside your workspace, type one line stating what you want and attach the upstream repo, e.g.:

Please speed up FindAllMarkers in https://github.com/satijalab/seurat using the pbmc3k dataset.

Then paste the Manager prompt:

141 lines · 7,806 chars

That’s the whole interaction. The Manager takes it from there.

What the Manager runs on your behalf

zyme init → Initialization → Auditor (init) → Optimization → Auditor (iterate) → Scaling validation → Portability check → Packaging. The agent-driven phases (Initialization, Optimization, Scaling, the optional Portability fix, and Packaging) run as zyme dispatch run --detach workers monitored with a check-in loop; the scaffold (zyme init), the auditor gates (zyme validate init / a manager-internal read of validate.tsv), and the portability gate (zyme scan --portability) are direct CLI calls, not dispatch workers. Per-task state lives in pipeline_runs/<date>_<run_name>/state.md so you can resume after a crash.

What to look at while it runs

zyme dispatch status                 # which phase, round count, last activity
zyme dispatch logs <task> -n 5       # tail recent worker output

If you want to interrupt, just close the coding-agent session. The Manager picks up where it left off when you paste the prompt again: it scans pipeline_runs/ and resumes the incomplete run.

When to skip it

  • Your first task: the per-phase pages teach you what each agent does.
  • You want fine-grained control over what gets accepted between rounds.

Otherwise: paste, walk away, nap, finished task.