Install
The CLI is included when you install SuperDialog:flow sub-tree (and --mode flow) is the legacy graph path.
superdialog generate
The default creation path. Bootstrap a validated simple-format playbook from
a plain-language prompt.
The output is parsed and compiled before it’s written, so anything
generate
produces is loadable. When to use: start every new agent here, then refine
the YAML by hand.
superdialog chat
Interactive terminal chat. No infrastructure, no Unpod account, no phone number.
Runs on the Playbook engine; defaults to ./playbook.yaml, then
./flow.json - any format is auto-detected.
When to use: during playbook (or legacy flow) design, prompt tuning, and
eval-dataset collection - before any voice infrastructure is involved.
superdialog optimize
Reflective prose optimizer: paired persona evals score targeted, prose-only
edits and emit improved YAML in your source format.
guidance / say, and writes back improved YAML. When to use: to
close the run → eval → improve loop without hand-tuning prompts.
superdialog playbook
Migration and direct playbook operations.
superdialog eval
A subcommand group: the playbook-vs-vanilla A/B harness plus the legacy
single-session audit. Full guide: A/B Evals.
eval run takes --modes, --agent-model, --director-model,
--talker-model, --judge-model, --user-model, --metrics, and --repeats
— see the A/B Evals guide. (For playbook persona evals
from Python, see run_eval in the
API Reference.)
superdialog benchmark
A separate RAGAS + deterministic harness: replays a dataset’s user turns at one
or more models and scores raw LLM vs with-SuperDialog against ground truth
in one big table.
benchmark uses the RAGAS 0.2.x line (the benchmark extra), while the A/B
eval harness uses RAGAS 0.4.3 (the ragas extra). They cannot co-install —
see A/B Evals → RAGAS.Legacy: flow graphs
Theflow sub-tree authors and inspects flow graphs. These still work;
superdialog generate writes a playbook instead.
--mode flow opts into the original graph runtime. See
Flows (legacy).
Traversal history (graph engine)
Any command running the legacy graph engine supports--traversal-dir. When
set, a timestamped JSON file is written per completed session capturing every
node visited, every turn, and all collected slot values:
agent.event_log.to_jsonl()).