running-coral-experiments

# Running CORAL experiments You drive a run with five verbs: **start → status → log/show → resume → stop**. Everything else is a flag on those or a deeper topic in the references. Prefer `coral <cmd> --help` over guessing flags. **Prereq:** a task (`task.yaml` + `seed/` + grader package) that passes `coral validate .`. No task yet → that's the `creating-a-coral-task` skill. Each runtime CLI must be installed and authenticated → the `setting-up-coral` skill. ## 1. Launch ```bash coral start -c task.yaml # auto-tmux session coral start -c task.yaml agents.count=4 agents.model=opus # dotlist overrides (no quotes needed) coral start -c task.yaml run.verbose=true run.ui=true # verbose logs + web dashboard coral start -c task.yaml run.session=local # foreground, no tmux ``` - **Dotlist overrides** (`key.subkey=value`) beat `task.yaml` for this run only — the clean way to sweep count/model without editing the file. - `run.session`: `tmux` (default, detachable) · `local` (foreground) · `docker`. - Each run lands in `results/<task-slug>/<timestamp>/`; agents work in isolated git worktrees and the grader daemon scores their commits. ## 2. Monitor ```bash coral status # agent health + leaderboard snapshot (the quick pulse) coral runs # active runs across tasks; --all includes finished coral ui --port 8420 # web dashboard: live leaderboard, logs, DAG ``` `coral status` answers "who's alive, how many ev...