Screen Recording permission

Updated October 24, 2026

Every screenshot, recording, and text capture reads your screen, and macOS lets an app do that only with the Screen Recording permission. OhMyShot asks for it the first time it needs it.

Granting it

While Screen Recording isn’t allowed, a small OhMyShot window opens at launch, and again when a command needs the permission.

Click Continue. The first time, macOS shows its own prompt; after that, Continue opens System Settings › Privacy & Security.
Turn OhMyShot on there.
Back in OhMyShot’s window, choose Relaunch.

Why the relaunch

macOS applies the permission only to new processes, so OhMyShot has to start again before it can see the screen. If captures come out blank, relaunch once.

If you build it yourself

macOS ties the permission to the app’s code signature. An ad-hoc signed build looks like a new app after every rebuild and loses it. To keep it, copy Config/Signing.local.xcconfig.example to Config/Signing.local.xcconfig and fill in your Apple Development team; a free personal team works.

To start over, this clears the Debug build’s permissions:

Scripts/reset-tcc.sh

Other permissions

Accessibility is asked for only by two features you turn on yourself: Auto-scroll in Scrolling Capture, and Text from apps (Settings › Text, off by default), which asks the app under a selection for the text it shows.
Input Monitoring is never asked for by Studio. When it is already on, a Studio recording keeps the keys you pressed so Studio can show them afterwards; Settings › Recording › Studio › Keep the keys pressed turns that off.

Automation needs it too

URL commands that capture the screen open the permissions window when Screen Recording is off, and the Shortcuts actions that capture fail with a message. See Automate OhMyShot.