# Quicksilver for macOS: Building the Launcher from Source

> Quicksilver is a free macOS launcher that learns your habits, and this repository holds the Objective-C source for the app itself. The build is documented on the project wiki, and the README's first instruction is a backup.

**quicksilver/Quicksilver** — Quicksilver Project Source

- Repository: https://github.com/quicksilver/Quicksilver
- Website: http://qsapp.com
- Stars: 2,931 · Forks: 291
- Language: Objective-C
- License: Apache-2.0
- Published: 2026-09-24 · Updated: 2026-09-24 · Language: en
- Canonical page: https://hysenlabs.com/projects/quicksilver-quicksilver

## What Quicksilver Is, and Which Repository You Are Looking At

Quicksilver is a macOS productivity application. The README describes it as "a fast and free macOS productivity application that gives you the power to control your Mac quickly and elegantly," and adds that it "learns your habits." That is a launcher in the classic sense: you trigger it, type, and act on what you find, and repeated choices shape what it offers next. The homepage is qsapp.com, where the about page and the download page live.

The repository is not the whole product. The README is explicit: "This repository contains the source code for the Quicksilver main app. It is also the place to browse existing issues and open new issues." So there are two audiences here. One is the macOS developer who wants to compile, patch or debug the app. The other is a user with a bug, who needs the issue tracker rather than the code. The `main` branch "contains the source for the currently released Quicksilver," which means a checkout tracks a release, not a staging area for unreleased work.

If you arrived expecting a cross-platform launcher, stop here. Everything in this repository is Objective-C and macOS-specific, and the README's own troubleshooting notes are about OS X services and AppleScript.

## The Plugin Architecture and Why the Map File Exists

The source tree is rooted at a `Quicksilver/` directory alongside `.gitmodules`, which tells you the app pulls in submodules rather than vendoring everything. A first-time contributor therefore has to initialize those before the project will build, and a shallow clone will not do.

The README points newcomers at `The_Map.md`, described as something that "should give you a head start if you're approaching this project for the first time." That file sits at the top level next to `CONTRIBUTING.md`, `GIT.md` and `SECURITY.md`. The presence of a map document is itself a signal: this is a long-lived codebase with enough surface area that the maintainers wrote a reading guide instead of expecting people to find their way through the directories.

What the README does not document is the plugin model in any detail, the catalogue format, or how triggers and actions are registered. Those are the parts a plugin author would need most. The README defers to the wiki for building and to two Google Groups for support, one general and one for developers. That is the honest state of the documentation: the entry points are named, the internals are not described in the repository itself.

## Backing Up Before You Build, and the Cache Command

The README's strongest instruction is not about compiling. It is about protecting your data. In bold: "Before building and testing Quicksilver, ALWAYS BACKUP your user data!" It then names the three paths that constitute that data.

```bash
~/Library/Application Support/Quicksilver
~/Library/Caches/Quicksilver
~/Library/Preferences/com.blacktree.Quicksilver.plist
```

Copy those three somewhere safe. The README's reasoning is that "if anything happens you can always restore the exact state Quicksilver was in before your were trying out this version" (the typo is in the original). This matters more than it sounds. A launcher that learns your habits stores those habits in its preferences and support directory, so a bad build can cost you a catalogue you spent months training.

When you move between versions, the README says you should "generally clear caches" with this command:

```bash
rm -r ~/Library/Caches/*Quicksilver
```

The glob is deliberate. It removes any cache directory whose name ends in Quicksilver, which is the pattern the app uses. Run it after a backup, not before, and expect the app to rebuild its caches on next launch.

## A First Real Use: One Quicksilver.app Only

The README documents a failure mode that has nothing to do with your code and everything to do with your filesystem. "Having multiple copies of Quicksilver.app on the system can cause issues with the Services System in OS X and AppleScript." The mechanism is specific: the pasteboard server at `/System/Library/CoreServices/pbs` sees multiple app packages, each with its own `Info.plist` defining the same services, and refuses to register them properly. AppleScript gets confused for the same reason.

So before you build a second copy, deal with the first one. The README's instruction is to zip any old Quicksilver.app packages you want to keep, so that "you only have one Quicksilver.app file on your filesystem." It then adds a step people skip: "do not forget to empty your trash after you deleted the older Quicksilver.app packages." Zipping rather than deleting is the interesting choice. It preserves the old build as an archive without leaving a second package on disk, which is exactly what the services system reacts to.

Once you have one package, the build itself is not described in the README. It says you "should be able to build Quicksilver by following the instructions as seen in the Quicksilver Wiki on Building Quicksilver," and links to qsapp.com/wiki/Building_Quicksilver. That page, not this repository, is where the Xcode steps live. If you cannot reach the wiki, you cannot follow the documented build path.

## Where the Source Repository Is the Wrong Tool

Most people who want Quicksilver should not clone it. The README answers the question directly under "Where to download Quicksilver?": visit QSApp.com and "download the right version for your operating system." There is no Homebrew formula, no package manager command and no install script in the repository. The build path runs through a wiki page and an Xcode project, which is a developer workflow, not an installation method.

The second limitation is documentation depth. The README covers backup, cache clearing and the multiple-copies problem. It does not cover the plugin API, the preferences format, or how the learning behaviour is implemented. Those are the questions a contributor will actually have, and the README answers none of them. It routes them to the developer Google Group instead.

The third is platform. This is a macOS application written in Objective-C. There is no Linux or Windows build, and nothing in the repository suggests one is planned. If your team runs mixed operating systems and wants one launcher everywhere, this is not it.

## Alternatives and the Difference in Approach

The natural comparison is with launchers that are distributed as signed binaries and updated automatically, where the user never sees a compiler. That model trades control for convenience: you get a version the vendor built and notarized, and you cannot patch a behaviour you dislike. Quicksilver's repository takes the other position. You get the Objective-C source, the issue tracker, and the responsibility for building it yourself.

A second comparison is with launchers built around an extension ecosystem with a documented, versioned API. The difference is where the documentation lives. Quicksilver's README points outward to the wiki and to a developer mailing list rather than describing the plugin interface in the repository. That is a real difference in onboarding cost: one model lets you read the API contract in the tree, the other asks you to join a group and ask.

Neither approach is wrong. But if your reason for adopting a launcher is that you want to write plugins against a stable, documented interface, the repository as presented here will send you to the wiki and the Google Group before you can judge whether the interface suits you.

## Licence, Maintenance and the Cost of Upgrading

Quicksilver is licensed under Apache-2.0. The README reproduces the standard notice: the software is distributed "on an 'AS IS' BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied." For a company considering a fork, that permissive licence is the relevant fact, but Apache-2.0 also carries notice and attribution obligations, and the repository ships a `LICENSE` file. Read it rather than relying on this summary; nothing here is legal advice.

On activity, the last push to the repository was on 2026-09-18, and the most recent release listed is v2.6.0 on 2026-04-19, preceded by v2.5.9 on 2026-03-30 and v2.5.8 on 2026-03-24. The repository is not archived. That release cadence is worth reading alongside the README's warning that you should back up before trying a build: versions move, and the support directory is the thing that survives a bad upgrade.

The upgrade cost is not in the code, it is in the state. Because the app learns your habits, a version switch means carrying `~/Library/Application Support/Quicksilver` and `~/Library/Preferences/com.blacktree.Quicksilver.plist` forward, and clearing `~/Library/Caches/*Quicksilver` on the way. Budget for that, and keep the backup until the new build has run for a while.

## Conclusion

Adopt Quicksilver from the source repository if you are a macOS developer who wants to work on the launcher itself, or if you run a build that the download page does not offer. Do not clone it expecting a packaged app or a supported install path: the README points end users to QSApp.com for downloads and to the wiki for build instructions. Before you build, verify two things: that only one Quicksilver.app exists on your filesystem, and that you have a copy of ~/Library/Application Support/Quicksilver, ~/Library/Caches/Quicksilver and ~/Library/Preferences/com.blacktree.Quicksilver.plist. Those three paths are the state you can restore if a build goes wrong.

## FAQ

### What is Quicksilver?

It is a free macOS productivity application that the README describes as letting you control your Mac quickly and elegantly, with the app learning your habits over time. The homepage is qsapp.com, and this repository holds the source for the main app.

### How do I download Quicksilver?

The README directs users to QSApp.com and says to download the right version for your operating system. The repository itself is the source code, not a download page.

### Can I build Quicksilver from this repository?

The README says you should be able to build it by following the instructions in the Quicksilver Wiki on Building Quicksilver, linked at qsapp.com/wiki/Building_Quicksilver. The build steps themselves are not reproduced in the README.

### Why does Quicksilver break Services or AppleScript on my Mac?

The README states that multiple copies of Quicksilver.app cause this, because the pasteboard server at /System/Library/CoreServices/pbs sees several packages defining the same services. Zip any old copies so only one Quicksilver.app remains, and empty the trash.

### What should I back up before trying a new build of Quicksilver?

The README names three paths: ~/Library/Application Support/Quicksilver, ~/Library/Caches/Quicksilver and ~/Library/Preferences/com.blacktree.Quicksilver.plist. It also suggests clearing caches with rm -r ~/Library/Caches/*Quicksilver when switching versions.

### What licence is Quicksilver released under?

Apache-2.0. The README reproduces the licence notice and states the software is distributed on an AS IS basis, without warranties or conditions of any kind.

## Sources

- [License: Apache-2.0](https://github.com/quicksilver/Quicksilver/blob/main/LICENSE)
- [Project website](http://qsapp.com)
- [quicksilver/Quicksilver on GitHub](https://github.com/quicksilver/Quicksilver)
- [README](https://github.com/quicksilver/Quicksilver/blob/main/README.md)
- [Releases](https://github.com/quicksilver/Quicksilver/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/quicksilver-quicksilver