FAQ

Home > FAQs > Not working

OpenCues not working? The troubleshooting checklist

Start with opencues doctor: read-only diagnostics across every host that name the problem and the fix. Then work down this list.

  • No key configured. LLM features need a provider key; a keyless install shows a visible hint at the _. opencues set-key cerebras <key> fixes it.
  • The keyword isn't leading the sentence. A keyword blank fires only when its keyword leads the sentence your _ ends. volume _ fires; please change the volume _ doesn't.
  • Spaced trigger mode. If blank-trigger-mode: spaced is set, the _ waits for a confirming space before firing.
  • Provider trouble. Rate limits fail over automatically if you've set both Cerebras and Groq keys; a dead key or outage is classified and named rather than failing silently.
  • A feature is simply off. Some surfaces are gated (sentence cues, ambient context); check config _ or OPENCUES.md.

Still stuck: opencues logs --tail streams the runtime log, opencues debug on makes it verbose, and a GitHub issue with your doctor output attached gets the fastest answer.

Related: Install · How blanks trigger · The missing key hint · Seeing the logs · GitHub repo