Wire it in
Assign aDialogMachine to ctx.session.dialog_machine - the SDK auto-wraps
it in a SuperDialogAdapter (see
Adapters). On the Playbook engine the
Talker streams real tokens straight to TTS:
Generate a playbook once with
superdialog generate and version-control the
YAML. You can edit it by hand and re-run superdialog chat to test - no voice
setup needed. See the SuperDialog Quickstart.Voice-specific patterns
These patterns are specific to running a SuperDialog agent inside a live call. For playbooks, tools, and sessions themselves, see the SuperDialog docs.Give tools call context
Define tools as closures inside your entrypoint to capture per-call data:Inject instructions mid-call
Push a runtime directive into the machine from a session hook:Switch flows mid-call (graph engine)
switch_flow is a graph-engine feature - build the machine with a FlowSet.
On the Playbook engine, model the same behaviour with
multiple journeys and interrupts in one playbook instead.
Detect completion
Both engines have terminal states. Afterrun() returns, check whether the
dialog finished or the caller hung up mid-conversation:
Go deeper
SuperDialog
The framework itself: playbooks, tools, sessions, CLI.
Embedding Guide: Unpod Voice
The full worked example: a SuperDialog agent inside an AgentRunner session.
Thinking in Playbooks
The mental model: checkpoints that gate outcomes.
Bring Your Agent
Prefer your own brain? Adapters for LangChain, OpenAI, Anthropic, HTTP.