What you’ll learn
-
How to run the Studio DAG in
:stepmode instead of auto-complete mode - How per-step callbacks expose dispatch/completion, output keys, and graph status
- How to pause, step, and resume a real deterministic Runic workflow without requiring provider credentials
Core idea
Step mode pauses between nodes and emits a structured history snapshot at each transition:
runic.set_mode(:step) -> runic.feed(topic) -> step loop -> runic.step / runic.resume
This page uses the actual step-mode command flow, not a replayed fixture timeline. Each click advances or resumes the shared deterministic Runic backend used by the studio auto-mode example.
Upstream command
mix run lib/examples/studio_step_demo.exs
Demo note
This interactive page uses deterministic local actions, but the runic.step and runic.resume transitions are real strategy transitions rather than a simulated replay.