Press _ on its note. Cues that only tell you something - a calendar clash, an advisory fact-check - can be silenced one at a time, so a single unhelpful cue never costs you the whole feature.
Two presses, two meanings
Put your cursor on the flagged text. The note says what to do:
⚠ clashes with dentist 10:00 (underscore to dismiss)
The first press quiets that cue for half an hour. Nothing lands in your text. The note then stays up for a few seconds and changes to (muted · underscore again to forget); press again while that is showing and the cue does not come back at all. Leave it alone and the note fades, and the cue is simply quiet for a while.
Only cues with nothing to offer
A cue that carries a rewrite keeps _ for cycling to it, because taking the suggestion is the useful answer there. Dismissal is for the ones that have nothing to swap in and only ever tell you something.
Silencing one never silences another
Each cue is retired on its own, including a similar one on the next line. Dismissal also goes by the wording of the note, so if the same point comes back to you phrased differently, it counts as a new cue.
Getting one back
Nothing is lost. Run opencues dismissals for the list of everything you retired, with a toggle per row:
opencues dismissals list prints it, opencues dismissals restore 2 brings one back by number or by a phrase from the list, and opencues dismissals clear brings back the lot. Nothing is written until you accept, so opening the list to look costs nothing. A running host picks up a restore within seconds, with no restart.
Half-hour silences are not written down
The short quiet lives only in the session you are in, so a fresh start clears it. Only the permanent kind is recorded, which is why the list stays short and readable. In the browser extension there is nowhere to save a permanent dismissal, so a second press quiets the cue for a day instead.
Related: What is an inline cue? · Catch mistakes as you type · Calendar-aware inline AI · GitHub repo