OpenCues' settings menu is a blank. Type config _ (or opencues settings _) and the _ expands into two words: a selector naming a setting and a satellite showing its current value. Cycle the selector to walk settings; cycle the satellite to change the value, which is written to your config and live within seconds.
Or say it in plain English
With fluid config (on in the shipped setup), you can skip the menu: enable debug logging _ flips debug-mode: on; voice mode off _ does what it says. A classifier maps your phrasing onto the known settings registry and nothing else: it can never route to user blanks or anything with side effects, and it falls through to a normal lookup when unsure.
Why this is safe
Settings have bounded values (on/off, a fixed list), so the classifier's whole output space is enumerable, validated against the registry after classification, and applied through the same code path as manual cycling. Free-form settings (like custom colour lists) are deliberately excluded and edited by hand in OPENCUES.md.
Related: What is a blank? · Hot-reload · GitHub repo