Foo AI Corp.
Help
Every question here is a real failure mode, and each answer says what is happening rather than only what to click. If none of them match, write to us — the address is on the contact page.
Voicecape cannot hear me
macOS asks for the microphone once, and if that prompt was dismissed the app never asks again — it can only send you to the setting.
Open System Settings → Privacy & Security → Microphone and switch Voicecape on. If it is already on and still silent, the microphone macOS is using may not be the one you are talking into: Voicecape follows the system default unless you pick a device in Settings → Microphone.
The words do not land in other apps
Typing into another application needs Accessibility, and reading the shortcut key needs Input Monitoring. They are two separate permissions and granting one does not grant the other.
macOS binds these permissions to the exact signed copy of the app. If you replaced Voicecape with a new download, the old grant no longer applies to it — remove the entry with the minus button, add the app again, and restart it. A permission that looks granted but does nothing is almost always this.
Holding fn switches my keyboard language
That is macOS, not Voicecape: by default the fn key is also the globe key, and letting go of it changes the input source or opens the emoji viewer.
Open System Settings → Keyboard and set “Press 🌐 key to” to “Do Nothing”. The key then belongs to Voicecape alone. If you would rather leave it to macOS, pick a different shortcut in Settings — Control+fn and ⌘⇧Space both work.
The shortcut stopped working
The key is read through a system event tap, and macOS tears that tap down when the permission behind it changes — including when you grant it. The app rebuilds the tap, but it cannot do that while it is being denied.
Open Voicecape once after granting Input Monitoring. If the shortcut is still dead, set it again in Settings: choosing a combination re-registers the tap, and a combination another app already owns is refused with the reason rather than accepted silently.
It is downloading a large file on first launch
The speech model runs on your Mac, so it has to be on your Mac. It is downloaded once, on first launch, and never again for that version.
Nothing you say is uploaded — the download is the model coming to you, not your audio going anywhere. On a slow connection you can leave the window open; the download resumes rather than restarting.
Nothing happens in a password field
That is deliberate. macOS marks secure text fields, and Voicecape refuses to type into them.
The refusal is not an error and there is nothing to fix. Password managers, lock screens and banking fields are all in this category.
The text ended up on my clipboard instead
Some applications refuse a direct write — Electron apps with an accessibility tree switched off, and a few terminals. Rather than losing the sentence, Voicecape puts it on the clipboard and says so.
Paste it where you wanted it. If it happens in the same application every time, that application is refusing the write, and switching insertion to Clipboard in Settings makes the behaviour consistent instead of surprising.
My trial ended and I have a licence key
Open Voicecape and enter the key in Settings. The key is in your purchase email; it looks like VC-XXXX-XXXX-XXXX.
One licence covers up to 3 Macs. Activating on a fourth asks you to release one first — do that in Settings → Licence on the Mac you are retiring. Reinstalling the same Mac does not consume a slot.
My dictations are not in History
History is off until you turn it on. Nothing is written to disk before you ask for it, which is why the list is empty on a fresh install.
Turn it on in Settings → History and pick how long to keep it. Anything dictated before that is not recoverable, because it was never stored.
My microphone is not in the list
The list is what macOS reports as connected right now. A device that is asleep, unpaired, or on a hub that has dropped will not appear.
Plug it in, then reopen Settings — the list is counted again each time you come back to the app. If you had pinned a device that is now gone, Voicecape falls back to the system default and says so rather than failing silently.