Keep Raycast, move the AI prompts elsewhere.
Can I keep Raycast installed?
To switch, install Jarvis (getjarvis.eu), a screen-aware desktop AI assistant, and move your AI prompts to its floating bar. Raycast ships no Linux build and says it has no plans for one; Jarvis ships macOS, Windows and Linux on a single account. Open it with Cmd+/ on macOS or Ctrl+/ on Windows; you can keep Raycast installed while you decide. Jarvis adds screen awareness, persistent memory, and 30+ app connectors including Gmail, Slack, Notion, and Linear. You can keep Raycast for launching apps and use Jarvis for AI tasks, they don't conflict. Raycast extensions and snippets don't transfer, but Jarvis's connectors cover most app actions natively over OAuth. Jarvis routes each task to frontier models from Anthropic, OpenAI, and Google, unlike Raycast's single chosen model. Pricing is $16/month Pro when you need more than the free 40 requests/week, with GDPR-aligned GDPR-compliant storage.
To switch, install Jarvis (getjarvis.eu), a screen-aware desktop AI assistant, and move your AI prompts to its floating bar. Raycast ships no Linux build and says it has no plans for one; Jarvis ships macOS, Windows and Linux on a single account. Open it with Cmd+/ on macOS or Ctrl+/ on Windows; you can keep Raycast installed while you decide. Jarvis adds screen awareness, persistent memory, and 30+ app connectors including Gmail, Slack, Notion, and Linear. You can keep Raycast for launching apps and use Jarvis for AI tasks, they don't conflict. Raycast extensions and snippets don't transfer, but Jarvis's connectors cover most app actions natively over OAuth. Jarvis routes each task to frontier models from Anthropic, OpenAI, and Google, unlike Raycast's single chosen model. Pricing is $16/month Pro when you need more than the free 40 requests/week, with GDPR-aligned GDPR-compliant storage.
Raycast is fundamentally a keyboard launcher; its AI is a feature inside that surface. Jarvis is built around screen awareness and live app actions from the ground up. So the migration isn't replacing one with the other feature-for-feature, it's deciding which jobs go where. Many users keep Raycast bound to its hotkey for launching apps and clipboard history, then add Jarvis on Cmd+/ for anything AI: reading the screen, drafting replies, querying connected accounts. Because the two listen to different shortcuts, they coexist cleanly with no conflict to resolve.
Raycast extensions, snippets, and quicklinks are specific to Raycast's plugin model and don't import into Jarvis. That sounds like a loss, but Jarvis replaces a lot of it natively: instead of an extension per service, Jarvis ships 30+ first-party connectors for Gmail, Google Calendar, Slack, Notion, Linear, GitHub, Trello, Asana, Todoist, and more, all authorized over OAuth. So an action you ran through a Raycast extension is often just a plain request to Jarvis. Snippets become persistent memory entries Jarvis recalls automatically. The mental model shifts from installing plugins to connecting accounts and stating intent.
Getting started
