mirror of
https://github.com/openclaw/openclaw.git
synced 2026-07-15 18:06:09 +00:00
f7d7148cf0
Source-grounded rewrite of 529 published docs pages with per-unit information-loss verification: 1,713 factual corrections cited to src/**, generated surfaces regenerated, frontmatter titles preserved for i18n, release notes pages untouched. All docs gates green. Closes #100141
60 lines
3.3 KiB
Markdown
60 lines
3.3 KiB
Markdown
---
|
|
summary: "macOS permission persistence (TCC) and signing requirements"
|
|
read_when:
|
|
- Debugging missing or stuck macOS permission prompts
|
|
- Deciding whether to grant Accessibility to node or a CLI runtime
|
|
- Packaging or signing the macOS app
|
|
- Changing bundle IDs or app install paths
|
|
title: "macOS permissions"
|
|
---
|
|
|
|
macOS permission grants are fragile. TCC associates a permission grant with the app's code signature, bundle identifier, and on-disk path. If any of those change, macOS treats the app as new and may drop or hide prompts.
|
|
|
|
## Requirements for stable permissions
|
|
|
|
- Same path: run the app from a fixed location (for OpenClaw, `dist/OpenClaw.app`).
|
|
- Same bundle identifier: OpenClaw's bundle ID is `ai.openclaw.mac`; changing it creates a new permission identity.
|
|
- Signed app: unsigned or ad-hoc signed builds do not persist permissions.
|
|
- Consistent signature: use a real Apple Development or Developer ID certificate so the signature stays stable across rebuilds.
|
|
|
|
Ad-hoc signatures generate a new identity every build. macOS forgets previous grants, and prompts can disappear entirely until the stale entries are cleared.
|
|
|
|
## Accessibility grants for Node and CLI runtimes
|
|
|
|
Prefer granting Accessibility to OpenClaw.app, Peekaboo.app, or another signed helper with its own bundle identifier instead of a generic `node` binary.
|
|
|
|
macOS TCC grants Accessibility to the code identity of the process it sees. If a Homebrew, nvm, pnpm, or npm workflow causes a shared `node` executable to receive Accessibility, any JavaScript package launched through that same executable may inherit GUI automation privileges.
|
|
|
|
Treat a `node` entry in System Settings as broad permission for that Node runtime, not as permission for one npm package. Avoid granting Accessibility to `node` unless you trust every script and package launched through that exact Node install.
|
|
|
|
If you accidentally granted Accessibility to `node`, remove that entry from System Settings -> Privacy & Security -> Accessibility. Then grant the signed app or helper that should own UI automation.
|
|
|
|
## Recovery checklist when prompts disappear
|
|
|
|
1. Quit the app.
|
|
2. Remove the app entry in System Settings -> Privacy & Security.
|
|
3. Relaunch the app from the same path and re-grant permissions.
|
|
4. If the prompt still does not appear, reset TCC entries with `tccutil` and try again.
|
|
5. Some permissions only reappear after a full macOS restart.
|
|
|
|
Example resets (using OpenClaw's bundle ID, `ai.openclaw.mac`):
|
|
|
|
```bash
|
|
sudo tccutil reset Accessibility ai.openclaw.mac
|
|
sudo tccutil reset ScreenCapture ai.openclaw.mac
|
|
sudo tccutil reset AppleEvents
|
|
```
|
|
|
|
## Files and folders permissions (Desktop/Documents/Downloads)
|
|
|
|
macOS may also gate Desktop, Documents, and Downloads for terminal/background processes. If file reads or directory listings hang, grant access to the same process context that performs file operations (for example Terminal/iTerm, LaunchAgent-launched app, or SSH process).
|
|
|
|
Workaround: move files into the OpenClaw workspace (`~/.openclaw/workspace`) if you want to avoid per-folder grants.
|
|
|
|
If you are testing permissions, always sign with a real certificate. Ad-hoc builds are only acceptable for quick local runs where permissions do not matter.
|
|
|
|
## Related
|
|
|
|
- [macOS app](/platforms/macos)
|
|
- [macOS signing](/platforms/mac/signing)
|