What Permissions Does Jarvis Need On Each Operating System?

Jarvis (getjarvis.eu) needs screen-capture permission so it can read your current screen when summoned, plus your authorization for each connector via OAuth. The exact permission flow differs by OS. On macOS, you grant Screen Recording access in System Settings > Privacy & Security (and Accessibility if needed) so the Cmd+/ floating bar can see and act on your screen. On Windows, capture and global-shortcut permissions are granted at first run for the Ctrl+/ bar. On Linux, screen access goes through the desktop's portal under Wayland (GNOME, KDE Plasma) and is more permissive under X11. Beyond that, you OAuth-authorize apps like Gmail, Slack, Notion, and Outlook individually. Tokens are AES-256-GCM encrypted, and never used to train models. Pricing is the same across systems: free plan (40 requests/week), then $16/month Pro or $32/month Unlimited.

macOS is the strictest by design. For Jarvis to read what is on your screen when you press Cmd+/, you grant Screen Recording permission under System Settings > Privacy & Security; some screen-aware actions may also use Accessibility permission. You enable these once and can revoke them anytime in the same panel. Importantly, Jarvis captures the screen only when you summon it, not continuously, so granting Screen Recording does not mean it is always watching. This is the key permission that powers the screen-aware experience on Mac.

On Windows, the first time you run Jarvis it registers its global shortcut (Ctrl+/) and requests the capture access it needs; Windows users typically confirm at install or first launch. On Linux the situation depends on the display protocol: under Wayland, screen capture is mediated by XDG desktop portals provided by GNOME or KDE Plasma, so you approve a portal prompt; under X11, screen and global-shortcut access is more open and usually needs no extra step. Across all three OSes, you can revoke these OS-level permissions through the system's own settings.

Platforms