macOS permissions
Ruru asks macOS for access only when a feature strictly requires it. Learn why each permission is needed, how to grant it, and our privacy guarantees.
Required permissions
1. Accessibility
Accessibility allows Ruru to locate your active text caret, read the surrounding context in the focused input field, and insert or replace answers directly back into your target app when generation completes.
- Why needed: Enables caret anchoring and direct response insertion into Xcode, VS Code, Notes, Slack, browsers, and terminals.
- How to grant: Open System Settings > Privacy & Security > Accessibility and toggle Ruru on.
2. Input Monitoring
Input Monitoring allows Ruru's global event listeners to detect summon gestures and track text selections across apps.
- Why needed: Listens for
⌥Space, double-Shift (⇧⇧), the@@trigger sequence, and selection highlights for quick actions. - How to grant: Open System Settings > Privacy & Security > Input Monitoring and allow Ruru.
Optional permissions
3. Screen Recording
Screen Recording is entirely optional. It is requested only when you explicitly attach the active window or screen to a prompt.
- Why needed: Captures window or display pixels to run Apple's on-device Vision OCR framework.
- If disabled: Ruru continues to function normally for text summoning, caret insertion, and CLI agents; only screen OCR capture is omitted.
Reviewing permissions
You can check the status of all permissions at any time from Ruru Settings:
Open Settings (⌘,) > Permissions to see live status indicators for Accessibility, Input Monitoring, and Screen Recording.