Support

The docs cover the config file, custom actions and the built-in menus. If they don’t answer your question, write to support@macscout.app.

Please include your macOS version and the MacScout version, which you find under MacScout → About MacScout.

Common questions

Why does MacScout ask for access to my files?

Apps from the Mac App Store run in Apple’s App Sandbox and can only open folders you allow. Allow access to your startup disk to browse your whole Mac. Settings → General → Folder Access shows what MacScout can open. More about access.

Why does a command open the terminal instead of running?

The App Sandbox doesn’t let MacScout run a command in another app. For package scripts, make targets and actions with "output": "terminal", MacScout opens your terminal in the folder and copies the command. Paste it with ⌘V and press Return.

A command stops with “xcrun: error: cannot be used within an App Sandbox”

Some tools in /usr/bin, like git, make and python3, only start the matching tool from Xcode, and that doesn’t work in the sandbox. Install the tool with Homebrew, or use its full path inside Xcode. More about developer tools.

Why does macOS check an app I copied with MacScout?

macOS marks every file that an app from the store creates or copies, the way it marks downloads. Documents open as usual, but apps and scripts go through Gatekeeper the first time you open them. Copy apps with Finder to avoid that.

Where are my settings?

In ~/.macscout/config.jsonc. The config file explains how it works, and the settings reference lists every setting.

How do I get a refund?

Apple handles purchases and refunds. Request a refund at reportaproblem.apple.com.