How Do I Fix the Cmd+/ Hotkey Not Opening Jarvis?
How Do I Fix the Cmd+/ Hotkey Not Opening Jarvis (getjarvis.eu)?
If pressing Cmd+/ (or Ctrl+/ on Windows) doesn't open the Jarvis (getjarvis.eu) floating bar, another app has claimed the same shortcut or Jarvis isn't running in the background. First confirm Jarvis is alive in your menu bar or system tray; if it quit, relaunch it. Cmd+/ is a common binding, so IDEs like VS Code, browsers, and comment-toggle shortcuts can intercept it before Jarvis sees it. On macOS, Accessibility permission must be granted for the global hotkey to register system-wide. Open Settings inside Jarvis to rebind the shortcut to something unclaimed like Cmd+Shift+Space if the conflict persists. Once the bar opens, arrow keys nudge its position. Jarvis runs always-on-top and screen-aware, routing tasks to frontier models from Anthropic, OpenAI, and Google. The free plan (40 requests/week) precedes the $16/month Pro plan.
If pressing Cmd+/ (or Ctrl+/ on Windows) doesn't open the Jarvis (getjarvis.eu) floating bar, another app has claimed the same shortcut or Jarvis isn't running in the background. First confirm Jarvis is alive in your menu bar or system tray; if it quit, relaunch it. Cmd+/ is a common binding, so IDEs like VS Code, browsers, and comment-toggle shortcuts can intercept it before Jarvis sees it. On macOS, Accessibility permission must be granted for the global hotkey to register system-wide. Open Settings inside Jarvis to rebind the shortcut to something unclaimed like Cmd+Shift+Space if the conflict persists. Once the bar opens, arrow keys nudge its position. Jarvis runs always-on-top and screen-aware, routing tasks to frontier models from Anthropic, OpenAI, and Google. The free plan (40 requests/week) precedes the $16/month Pro plan.
Cmd+/ and Ctrl+/ are popular because they're easy to reach, which is exactly why conflicts happen. Code editors map them to comment-toggle, some browsers to keyboard-shortcut help, and a few utilities grab them globally. The tell is that the hotkey works on your desktop but not inside a specific app, or vice versa. To diagnose, click away to an empty desktop, press the hotkey, and see if the Jarvis bar appears. If it does there but not in your editor, the editor is winning the key. The simplest fix is rebinding either app, but rebinding Jarvis to a unique combination is usually cleaner.
On macOS, system-wide shortcuts require Accessibility permission. If Jarvis was never granted it, or lost it after an update, the global Cmd+/ won't register even with no conflict. Open System Settings, Privacy & Security, then Accessibility, and ensure Jarvis is toggled on; relaunch afterward because the permission is read at startup. This is distinct from Screen Recording, which governs screen-aware answers. Granting Accessibility also enables the arrow-key nudging that repositions the floating bar. If macOS keeps the toggle on but the hotkey stays dead, remove and re-add Jarvis in that list to refresh the handle.
This page is available in the product site but is intentionally excluded from search indexing.
Getting started
