Run Speakey as administrator
Most of the time Speakey types into whatever window has focus. But every so often you dictate into an app and nothing lands — no error, just silence. Nine times out of ten that app is running as administrator, and this setting is the fix. Windows only.
Why it happens
Windows enforces a security boundary between normal and elevated programs: a program running at normal privilege isn't allowed to send keystrokes into a window running as administrator. So if you launch a game, a terminal, or a tool elevated — or you run Discord as admin so it can capture in-game keybinds — a normal Speakey is walled off from it. The hotkey may not even register while that window is in front.
The only way across that boundary is for Speakey to run elevated too. That's what this setting does.
Turning it on
Go to Settings → System and enable "Run Speakey as administrator." You'll see a single Windows permission prompt. After that, Speakey starts elevated automatically every time you log in — no prompt on subsequent launches — and it can type into elevated apps like any other window.
You approve the elevation once. Speakey registers a startup task so future launches come up elevated on their own. Toggling it off takes full effect after a restart; turn it off and CapsLock-clean uninstall and reboot leave nothing behind.
Is it safe?
It's off by default and entirely opt-in, because elevation is a real privilege bump — while it's on, Speakey runs with administrator rights. Nothing about how Speakey works changes: it still runs entirely on your machine, still sends nothing to the cloud. Leave it off unless you actually need to dictate into an elevated app; flip it on the moment you do.
This is a Windows-specific wall. On Linux, Speakey injects text at the input layer and already reaches every window once you've granted input access during setup — so there's no "run as administrator" toggle to worry about.