Permissions
Three switches, granted once. Each one buys exactly one capability, and this page says plainly what each does and does not allow.
The three permissions
| Permission | What it buys | Its limit |
|---|---|---|
| Microphone | Hearing you | The app listens only while the key is held. Nothing is captured before or after. |
| Accessibility | Typing for you | It presses ⌘V on your behalf. It does not read what is on your screen. |
| Input Monitoring | Feeling the key | One key — the one you choose. Every other keystroke passes straight through. |
All three are macOS-level grants. macOS holds the keys, not the app: you can inspect or revoke any of them at any time in System Settings, and the app has no way to grant itself anything.
Granting them
First-run onboarding asks in order — Microphone, then Accessibility, then Input Monitoring — and unlocks each row only when the previous one is granted. That ordering is deliberate: it keeps three simultaneous system dialogs from stacking up on top of each other.
You can also grant or re-check them later from Dashboard ▸ Settings ▸ Permissions, which shows each one as granted, or offers a Grant… button, or an Open System Settings button when a permission was previously denied.
This is the most common permissions snag, and it is usually Accessibility or Input Monitoring. macOS sometimes shows the prompt but does not add the app to the list. The fix: open the relevant pane in System Settings ▸ Privacy & Security, click +, and pick OpenVoiceFlow from your Applications folder. The app watches for the change and picks it up within about a second — no relaunch needed.
Checking them by hand
Open System Settings ▸ Privacy & Security and look in:
- Microphone — OpenVoiceFlow should be on.
- Accessibility — OpenVoiceFlow should be on.
- Input Monitoring — OpenVoiceFlow should be on.
If a toggle is present but off, turning it on is enough. If the app is missing from a list entirely, add it with +.
macOS ties these grants to the app's code signature and location. Moving the app out of /Applications, or restoring it from a backup, can invalidate a grant. If dictation suddenly stops after an update, re-checking these three panes is the first thing to try.
What is never asked for
OpenVoiceFlow does not request Screen Recording, Full Disk Access, Automation, Contacts, Calendar, or Photos. It is not sandboxed, but its entitlements request only two capabilities: audio input, and outbound network access used solely for model downloads, update checks, and — if you turn it on — cloud cleanup.
Frequently asked
Why does a dictation app need Accessibility?
Accessibility is the macOS permission that lets one app send keystrokes to another. OpenVoiceFlow uses it to press Command-V on your behalf so text lands at your cursor. It does not read your screen contents. Without it, the app copies the text to your clipboard and asks you to paste manually.Why does it need Input Monitoring?
Input Monitoring lets the app notice your push-to-talk key being held while you are working in a different app. Only the one key you choose is acted on; every other keystroke passes straight through untouched.Can I revoke a permission later?
Yes. Open System Settings, Privacy and Security, then the relevant pane, and turn OpenVoiceFlow off. The app detects the change within about a second and updates its status. Revoking Microphone or Input Monitoring stops dictation; revoking Accessibility falls back to clipboard paste.Documentation for OpenVoiceFlow 0.5.5 · last updated 2026-07-31. Something wrong or missing here? That is a bug — tell us at shimoverse@gmail.com.