macOS Permissions

What Omniscio asks your Mac for, why, and what that repeating notification actually means.

The short version

Every permission below is asked for at the moment you use the feature — never at startup, never in the background — and all but one are opt-in. The exception is Automation → Terminal: it belongs to core flows that no toggle gates (signing in to an AI provider, installing a developer tool), so it can appear the first time you do either, even with every optional feature switched off. The optional setup step that lists permissions is skippable and never triggers a macOS dialog unless you click.

Omniscio never changes your system volume level, and it never uses System Events for sound. The one audio-output feature in the app is the optional Mute other sounds while dictating switch under Settings → Voice Control → Behavior. With it on, your speakers are silenced for as long as a dictation runs and then put back exactly as they were when it ends or you quit. If Omniscio crashes mid-dictation, the sound comes back the next time you open it. It mutes and unmutes — it never changes the level — it exists only on macOS and Windows, and it is off unless you switch it on. The confusion is understandable: the System Events prompt asks permission to control System Events, macOS's general scripting gateway — it can do far more than we use it for. macOS offers no way to grant just "paste text", so the prompt reads far broader than the actual use — and it only appears at all once you dictate, or if you turn meeting detection on.

Bluetooth is not requested. Older builds declared it by accident — inherited boilerplate from the framework Omniscio is built on, with no code behind it. It has been removed, and a build check now fails if it ever returns.

What each permission is for

"Omniscio was prevented from modifying apps on your Mac"

This is the App Management permission, and it behaves unlike every other one: macOS reports it as a notification with no dialog and no reason. That is why it can repeat endlessly with nothing for you to answer.

Why Omniscio is named. macOS blames the app that started a command, not the command itself. Omniscio runs commands for you — installing a tool, cleaning a build folder, tearing down a workspace. If one of those touches an installed app's files, macOS reports it against Omniscio, even though Omniscio never touched that file.

Omniscio never modifies your other apps, and it never asks for App Management. There is no way for an app to request that permission in the first place.

Finding out what was blocked

Open Settings → Diagnostics → Blocked by macOS App Management and choose Check what was blocked. macOS records the exact file in its own privacy log; Omniscio reads it back and shows you the app, the command, and the path, for the last 24 hours.

Then:

One caveat the card states plainly: the macOS log entry doesn't record which app was responsible, so the list shows every App Management block on your Mac in that window. Some may have nothing to do with Omniscio.

If you said "Don't Allow", or it still does not work

macOS remembers a refusal: once you click Don't Allow it will not ask again on its own. You can grant any of them at any time in System Settings.

If Omniscio is not in the list at all, that prompt has never been triggered: use the feature once and macOS asks, then the app appears in the list.

Screen Recording only takes effect after you quit and reopen Omniscio. macOS keeps the old state until the app restarts, so a recording started straight after you grant it can still come out black. Quit Omniscio completely (not just close the window) and open it again.

A black, empty or silent recording means Screen Recording is not actually granted. That is the symptom to check first — follow the Screen Recording path above, then restart the app. App Management has its own recovery path in the section above.

Related: Privacy Policy · Back to Omniscio · Still broken? · support@omniscio.com · Do Not Sell or Share My Personal Information