ueli
ueli is a keyboard-driven application launcher and search utility for desktop workflows. This page covers command discovery, indexing scope, hotkey conflicts and privacy-conscious configuration.
What ueli provides
ueli provides a keyboard-first launcher for starting applications, searching configured locations and running small actions without navigating several menus. Its value depends on a clean command vocabulary and an index scope that matches the user's workflow; a broad index can make results noisy and expose names that should remain private.
Configuration and data boundaries
Choose a hotkey that does not conflict with the operating system or another launcher. Start with a small set of application and document locations, then add folders only when the result quality justifies it. Review extensions, shell actions and custom commands before enabling them, especially on a shared desktop.
Maintenance note
This page reviews ueli for keyboard launching, scoped desktop search and command maintenance. Content review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave ueli to this cloud drive
Baidu Netdisk
Save ueli to this cloud drive
ueli desktop launcher setup guide
Configure one launcher shortcut, index only a small test folder and verify that search results, custom commands and privacy boundaries match the intended workflow.
Before you start
- List the applications and folders that should appear in search results.
- Choose a shortcut that is free on the operating system and other productivity tools.
- Keep a note of custom commands so they can be reviewed or recreated later.
Installation steps
- 01
Open the launcher settings
Install and start ueli, open its settings and confirm the process is running for the intended desktop account rather than a shared service account.
- 02
Set the shortcut and search scope
Assign a free hotkey, add one low-risk folder and check whether application names, files and actions appear in the expected order.
- 03
Add commands gradually
Create one custom command at a time, test its input and output, and record the command text before enabling it in the daily workflow.
Quick start
- 01
Tune result quality
Remove duplicate paths and noisy file types, then compare a few common queries so the launcher favors useful results over a complete but unwieldy index.
- 02
Check hotkey conflicts
Temporarily disable other launchers or shortcuts when diagnosing a missed invocation, then keep a single documented owner for the global hotkey.
- 03
Review sensitive locations
Exclude private folders and generated caches that do not need search exposure, and recheck the index after moving or renaming a directory.
Usage tips
- Keep custom commands short, explicit and reversible; avoid commands that silently delete or overwrite files.
- Use separate configuration notes for work and personal profiles when their search scopes differ.
- Recheck extensions and command inputs after application updates or shell changes.
Troubleshooting and uninstall
Why does the shortcut do nothing?
Check whether another application owns the key combination, whether ueli is running in the current session and whether the operating system granted the required keyboard-access permission.
Why are search results incomplete or noisy?
Inspect indexed paths, excluded extensions and stale cache entries, then adjust one scope rule at a time and rebuild or refresh the index if the application provides that action.
- Export useful settingsRecord the shortcut, search paths and custom commands that should be retained before closing the launcher.
- Remove the launcher and indexUninstall ueli through the operating system and remove its local index or cache after confirming that no other workflow depends on those files.
Frequently asked questions
Does ueli replace the operating system's file search?
It provides a keyboard-driven launcher and configured search layer; the operating system's own indexing and permissions still determine which files can be discovered.
Should every folder be indexed?
Start with the smallest useful scope. Exclude private, temporary and high-churn folders unless searching them is an explicit requirement.
Does the download require an extraction code?
The Quark entry does not require one; the four-character code for the Baidu entry is shown beside its download entry.