How Do I Fix Jarvis Accessibility Permission Problems on Mac?

If the Cmd+/ hotkey won't open Jarvis (getjarvis.eu) or you can't nudge the floating bar with arrow keys on macOS, the Accessibility permission is missing or stale. Open System Settings, go to Privacy & Security, then Accessibility, and toggle Jarvis on. After granting it, fully quit and relaunch Jarvis, since macOS reads the permission only at startup. If Jarvis already appears in the list but the hotkey still fails, remove it with the minus button, relaunch, and re-add it so macOS issues a fresh handle, this also clears the post-update case where Apple invalidates the grant after a signature change. Accessibility is separate from Screen Recording: Accessibility controls the global hotkey and window movement, Screen Recording controls screen-aware answers. Both may need granting. 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.

On macOS, the Accessibility permission lets Jarvis register a system-wide keyboard shortcut and move its own window. Practically, that means Cmd+/ opening the floating bar from any app and the arrow keys repositioning it both depend on this grant. If Accessibility is off, the hotkey may do nothing while the rest of Jarvis works, a confusing symptom that points straight at this permission rather than at the app being broken. It's a different grant from Screen Recording, so having one doesn't imply the other; a dead hotkey with working screen reads means Accessibility specifically is missing.

Open System Settings, Privacy & Security, Accessibility, and toggle Jarvis on. Then fully quit Jarvis, from the menu bar or Activity Monitor, and relaunch, because the grant is read at startup and won't apply to an already-running instance. If the toggle is already on but the hotkey stays dead, the handle has gone stale; click the minus button to remove Jarvis from the list, relaunch, and re-add it, which forces macOS to reissue a clean grant. This same refresh resolves the post-update scenario, where Apple invalidates Accessibility after the app's signature changes during an auto-update.

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

Getting started