The note is the line OpenCues shows under a flagged word: what pressing _ would give you, and, when there are several, how many alternatives remain. Every other feature renders through it.
Dimmed at rest; selected, with the note, when the cursor is on it.
Dimmed marks that alternatives exist, without showing them. The word stays readable and nothing else on the line changes. When the cursor reaches the word it becomes selected and the note appears underneath; moving away, or editing the word, removes both.
How it is drawn is up to the host.
The note is painted over the display, never written into your text, so it cannot be sent or copied and there is nothing to delete before pressing enter. A long note wraps onto further lines and the content below moves down to make room.
An optional emoji, then the destination; with three stops or more, a count and the upcoming alternatives.
An emoji means a detected problem; no emoji means an optional improvement. The distinction is visible before reading the text, so an error and a suggestion can be triaged at a glance.
Two stops have no count. Three or more count down.
A note with one alternative names it, and after the press says what it was: an action and its undo, not a rotation. With three stops or more the count starts at the total and decreases as you cycle. It never reaches zero: your original word is one of the stops, so there is always a next press.
With three stops or more, the list after the count shows where the next presses go, in order, rotating as you cycle. It always shows destinations, never the word already in the line.
The hint says what the next press does: (underscore to correct) on a spelling, (underscore to fix) on a check, (underscore to apply) on a tip or a rewrite, and (underscore to revert) once the next press restores your text. The ones that teach a key are shown until you first press on that note, then dropped for it; a host restart shows them again.
The note moves to the status display.
Plain browser fields cannot show per-word colour, so word cues stay off there entirely; underscore requests still work. Rich editors in the browser show the note inline as terminals do.