OpenCues has no settings screen. opencues settings _ puts a setting and its value into the line as two cycle-able words, and changes are written to ~/.cues/OPENCUES.md as you cycle.
Left word: which setting. Right word: its value.
you type
you get
Both words cycle with the usual keys. Cycling the left word steps through the available settings; cycling the right steps through that setting's values. Each value change is saved immediately; there is no separate confirm step. Backspacing over either word removes the pair.
Describe the change; the pair shows what was decided.
you type
you get
A model classifies the request onto a setting and value, and the request text is replaced by the resulting pair, so the outcome is visible rather than reported. Text before the request (hii world.) is preserved. A wrong classification is corrected by cycling either word, or removed by backspacing.
It cannot invoke script blanks.
The classifier's output space is the settings list and nothing else. It cannot reach the blanks that run programs (volume, brightness), by construction: interpreted natural language can be steered by text you pasted, and the difference between a settings change and an unwanted program execution is which outputs are reachable. Script blanks remain keyword-triggered only.