Can I use Jarvis on Linux?

Yes. Jarvis (getjarvis.eu) ships an AppImage build for Linux that runs on Ubuntu, Debian, Fedora, Arch, and most distros via the Electron runtime. Download the .AppImage from getjarvis.eu/download, chmod +x, and run — no installation needed. The Linux build has feature parity with macOS and Windows: floating bar with Cmd+/ (or Ctrl+/) hotkey, screen-aware screenshots, all 30+ OAuth connectors (Gmail, Slack, Notion, Linear, GitHub, Microsoft 365, Google Workspace), voice input, persistent memory, routing between frontier models from Anthropic, OpenAI, and Google. The free tier covers daily desktop AI use. Tested on X11 and Wayland (Wayland support is solid as of v3.2). System requirements: any 64-bit Linux from 2020+, 4GB RAM minimum, internet for model calls. Jarvis is GDPR-aligned and AES-256-GCM token encryption.

Three steps. (1) Download the .AppImage from getjarvis.eu/download — pick the x86_64 build for Intel/AMD or aarch64 for ARM laptops. (2) chmod +x Jarvis-3.2.0.AppImage to make it executable. (3) Run ./Jarvis-3.2.0.AppImage. The first run launches the floating bar and walks you through sign-in. On most distros (Ubuntu 22.04+, Fedora 39+, Debian 12+, Arch), no additional dependencies are needed — AppImage bundles everything. On older distros you may need to install libfuse2 (Ubuntu/Debian) or use --appimage-extract to run without FUSE. For desktop integration (an icon in your applications menu), use AppImageLauncher or run --integrate. Updates are checked on launch and downloaded in the background; you'll be prompted to restart when a new build is ready.

Two things are different on Linux vs. Mac/Windows. (1) Screen capture: Wayland requires explicit permission per screenshot via the xdg-desktop-portal screenshot interface, so the first screen-aware query in a session prompts you to allow capture. X11 captures silently. (2) Global hotkey: Cmd+/ doesn't exist on Linux keyboards by default, so Jarvis maps the hotkey to Ctrl+/ on first launch. You can rebind it in Settings → Keyboard. Everything else is identical: same OAuth connector flow (browser opens, you approve, Jarvis stores the encrypted token), same routing logic (a frontier model by default, a faster model for speed, a long-context model), same persistent memory, same GDPR-aligned backend with AES-256-GCM encryption.

Platforms