Quicksilver Problems & Issues
Real user-reported problems, complaints, and limitations for Quicksilver. Based on analysis of 11 signals.
Overall score: 55/100
Issues by Category
"Interface could not be loaded. Switching to bezel" and then nothing works
A growing number of reports on Tahoe and macOS 27 describe the interface failing to load, menus not responding and settings being unreachable. Clearing caches helps temporarily for some; a maintainer said in October 2026 that a fix was being tested.
Quicksilver crashes randomly on Sequoia and Tahoe
Users on macOS 15 and 26 report Quicksilver quitting at random with no clear trigger, some running a helper app just to relaunch it. A long GitHub thread (#3062) on intermittent crashing has stayed open since August 2025; several 2.5.x and 2.6.0 releases fixed specific crash causes but not all.
Quicksilver breaks after every major macOS update
Each macOS release (Mojave, Sonoma, Sequoia, Tahoe, macOS 27) brought a wave of permission, catalog and crash problems, from Safari no longer found in the catalog to the app doing nothing at all after updating to macOS 27.
In-app update freezes Quicksilver
Some users report the app freezing on "Updating Catalog" when installing app or plugin updates from Settings, forcing a force-quit; the workaround is downloading the DMG manually.
Why is Quicksilver using so much CPU?
Reports of 35% to 95% idle CPU, spinning wheels and in extreme cases tens of GB of RAM. Causes discussed include the process monitor reacting to apps (like Safari web processes) relaunching constantly and catalogs that scan too deep; no complete fix as of late 2026.
Quicksilver keeps asking for permissions every launch
On Sonoma and Tahoe users see permission prompts (Accessibility, Full Disk Access, Calendar, data in other apps) again and again, even when System Settings shows them as granted. There is no way to skip optional permissions yet; a "don't ask again" option has only been proposed.
Tiny volunteer team and slow fixes
Quicksilver is maintained by a few volunteers; press coverage notes updates usually arrive about once a year, and around 80 issues are open on GitHub. Support is a Google Group and GitHub issues, where maintainers mostly ask for logs rather than offering quick fixes.
Quicksilver feels outdated next to Raycast and Alfred
Forum users call it less stable, less polished and missing many features compared with Alfred and Raycast. Some removed animations went away when private Apple APIs were disabled in 2.4.2.
Steep learning curve: catalog, scan depth and three-pane grammar
New users find that files are missing because default scan depth is shallow (Desktop 1 level, Documents 2), search modes change by accident, and features hide behind plugins and disabled actions. The official FAQ is largely about these surprises.
Plugins outdated or broken (Chrome bookmarks, Mail, Recent Documents)
Plugins depend on volunteers too: Chrome bookmarks stored in a Google Account are missing, recent documents broke again in 2026, and Mail/Gmail plugins only got Apple Silicon updates in early 2026. The Emojis plugin was linked to crashes in 2026.
Quicksilver triggers not working after restart or not saving
Custom triggers stop working after a restart when they point at objects not in the catalog, or never save when the Triggers.plist file is not writable or refers to removed plugins.
Regret Patterns
Common reasons users regret choosing Quicksilver.
Lost a morning after a macOS update
Users upgrade macOS and find Quicksilver crashing, prompting for permissions or showing no interface, then spend time clearing caches and reading GitHub threads.
Catalog set too deep, Mac slowed down
Adding the whole home folder or infinite-depth sources makes Quicksilver eat CPU and memory.
Never got the grammar and went back to Spotlight
New users find the three-pane model, catalog and plugin setup confusing and give up.
Waited months for a fix that never came
Crash and CPU threads stay open for a year or more because the volunteer team is small.
Moved to Alfred or Raycast and didn't look back
Users who felt Quicksilver was a dead product switched and found the alternatives more polished.
When Quicksilver Breaks Down
Specific scenarios where Quicksilver fails or underperforms.
After a major macOS upgrade
Permissions reset or are reported wrongly, actions fail, and the interface may not load until caches are cleared or the app is updated.
Huge catalog (home folder, network drives, infinite depth)
Scanning never ends, CPU stays high and memory climbs.
Safari or other apps relaunching processes constantly
The process monitor reloads repeatedly and causes high idle CPU and spinning wheels.
App installed outside /Applications (external drive)
Plugins and interface files fail to load (too many open files) and the app does nothing.
Installing app and plugin updates from Settings
The update dialog can freeze on Updating Catalog and needs a force-quit.
Migrating an old Application Support folder to a new Mac
Copied old settings, mnemonics or shelves can make Quicksilver crash; a clean start is more reliable.