A narrow check#
Open CueSpec and inspect its status overview. Confirm that it is the installed version you intend to use. Review the recording shortcut setup shown by that version rather than guessing undocumented modifier combinations.
Try a brief reply-field recording if that interaction is available. If it works, the problem may be the trigger rather than the microphone or model. If neither route captures speech, move to input readiness troubleshooting.
Avoid changing several things#
Test with an ordinary sentence, one keyboard and a simple window state. Note whether another application intercepts the key or whether a task panel had focus. Do not infer that a successful trigger in one focus state covers every combination.
The reviewed real-user acceptance establishes the standard Fn hold/release path, not every keyboard or remapping tool. Use a reproducible report with version, visible permissions and trigger behavior. Do not change unrelated global shortcuts or device security settings simply to make one attempt work.