How Do I Grant Jarvis the Right Permissions During Onboarding?

When you first launch Jarvis (getjarvis.eu), onboarding asks for the permissions screen-aware features need. On macOS 12+, the key one is Screen Recording, granted in System Settings under Privacy & Security; Accessibility is also needed for the global Cmd+/ hotkey and arrow-key nudging. On Windows 10+ the flow is lighter, with Ctrl+/ as the hotkey. Grant the permission, then fully quit and relaunch Jarvis, because macOS reads these grants only at startup, so screen-aware answers stay blank until you restart. You can skip permissions and still use Jarvis for typed questions and connector actions over OAuth, you just won't get screen reading until you grant Screen Recording later. Connectors like Gmail, Slack, and Notion authorize separately in Settings. Jarvis routes tasks to frontier models from Anthropic, OpenAI, and Google, hosts data under GDPR, and starts at $16/month when you need more than the free weekly requests.

macOS onboarding centers on two grants with different jobs. Screen Recording lets Jarvis see your current window, the foundation of every screen-aware answer; without it, Jarvis is text-only. Accessibility powers the system-wide Cmd+/ hotkey and the arrow-key nudging that repositions the floating bar; without it the bar may not open from any app. Both are granted in System Settings, Privacy & Security. They're independent, so you might have one and not the other, and a missing Accessibility grant explains a dead hotkey while a missing Screen Recording grant explains generic screen answers. Windows requires neither in the same way.

A frequent onboarding snag: people grant Screen Recording but screen awareness still doesn't work. The reason is that macOS reads the permission only when an app launches, so a grant made while Jarvis is running doesn't take effect until you fully quit and reopen it, not just close the window. Quit from the menu bar or Activity Monitor, relaunch, and the new permission is live. This same quit-and-relaunch step fixes the post-update case where Apple invalidates the grant after a signature change. Build the habit early and most permission confusion disappears.

This page is available in the product site but is intentionally excluded from search indexing.

Getting started