Deep links - the abliteration:// URL scheme
Abliteration registers itself as the handler for abliteration:// URLs so the site (and other apps) can hand off a specific model directly to the runtime.
Short answer
Abliteration registers itself as the handler for abliteration:// URLs so the site (and other apps) can hand off a specific model directly to the runtime. Clicking Open in app on any model page at abliteration.org opens the model inside Abliteration and starts the download at the recommended quantization. Old infrahuman:// links still work.
Detailed explanation
Registered scheme, same on Windows and macOS. When Abliteration installs, the operating system records it as the handler for two URL schemes:
abliteration://- the current scheme, the one the site uses todayinfrahuman://- the legacy scheme from before the rebrand, kept alive so old bookmarks and shared links keep working
Any browser or app on either platform that hits either scheme routes the URL to the running Abliteration instance, or launches the app if it is closed and hands the URL off once the window is ready. On Windows the mapping is stored in the Registry under the app package; on macOS it comes from the LSHandlerRoleAll entries in the app bundle’s Info.plist, which Launch Services picks up the first time the app is opened from /Applications.
Supported actions.
abliteration://install-model?url=<direct-GGUF-URL>&name=<file-name>&size=<bytes>&sha256=<hex>&source=abliteration.org- the current format. The site opens the Open-in-Abliteration dialog, resolves the repo’s GGUF files through the HuggingFace proxy, and when you pick a quantization fires a deep link with the direct file URL plus size and (for LFS files) SHA-256 pre-filled. The app validates the hash on download and refuses to launch a mismatched file. The oldabliteration://open?action=add-model&repo=<slug>format is retired and the app no longer handles it.abliteration://health- a no-op that opens the app if it isn’t already running. The site uses this as a light “ping the handler” check without needing to touch the local HTTP bridge.
Any unknown action opens the app to its default view - never a loud error, never a crash.
Single-instance behaviour. If Abliteration is already running (window open or in the tray), the URL routes into that existing instance rather than launching a second copy. See System tray for how the process persists.
Why it matters
The catalog at abliteration.org lists thousands of models. Clicking one and copy-pasting the repo path into an app is friction. A single Open in app link that hands off the exact model, at the exact quantization your rig can actually run, is the whole point of a first-party runtime - the browser knows what you clicked, the app knows what will fit, and neither needs the other to describe it.
In Abliteration specifically
Repo paths in the URL match Hugging Face’s author/name shape verbatim (e.g. huihui-ai/Huihui-Qwen3-30B-A3B-abliterated-GGUF). The app does not invent its own naming, it hands the repo to the existing Hugging Face resolver.
On Windows, the rebrand kept the same underlying MS Store identity, so updating an older install of Infrahuman to Abliteration preserves your model library, chats, and settings. That is also why infrahuman:// still resolves; old links share the same underlying handler registration. On macOS, the Mac build ships fresh under the abliteration:// scheme; the legacy infrahuman:// handler is registered too, for parity with Windows links shared across platforms.
Deep links only route into a running app instance if the app is actually running. On both platforms Abliteration stays alive after you close the window - in the Windows tray or in the macOS menu bar (see Menu bar and tray) - so abliteration:// clicks land instantly. If the app is fully quit, the first abliteration:// click has to relaunch it, which takes a second or two before the model page opens.
Related
- Menu bar and tray - how the app stays running so deep links hit an existing instance
- Fit-check dialog - the quantization-picking logic reused for
action=add-model - Local HTTP bridge - the sibling site-integration, for hardware data rather than actions