Get the app

The site says "install the app" even though I have the app on macOS

The Mac build only speaks to abliteration.org when it is running from the Applications folder. Launched from Downloads, the loopback listener is blocked by the macOS sandbox.

Short answer

On macOS, the local HTTP bridge that the abliteration.org catalog probes on 127.0.0.1:47821 is only reachable when Abliteration is running from the Applications folder. If you double-clicked the app while it was still in Downloads or somewhere else outside /Applications, macOS is running it inside a stricter quarantine that blocks the loopback listener. The site still sees silence and falls back to the yellow “install the app” plate.

Detailed explanation

What the site is looking for. Model pages on abliteration.org fetch http://127.0.0.1:47821/health in the background. When they get an answer, compatibility chips light up in exact green, amber, and red against your actual RAM, and the plate at the top of the catalog reads CONNECTED. When they get nothing, the page falls back to a coarse browser guess and the plate reads GUESS with a “Get the app” button. See Local HTTP bridge.

Why the message persists even when the app is open. macOS quarantines every file downloaded from the internet. An app running under quarantine has restricted network entitlements, including the ability to bind a listening socket on the loopback interface. macOS clears the quarantine flag on an app when it lives in /Applications and has been launched from there. Running the app from the Downloads folder, or from anywhere else outside /Applications, leaves the flag in place and the bridge cannot start; the site sees the same silence it would if the app were not present at all.

How the bridge should behave once it works. With the app running from Applications, opening any model page on abliteration.org flips the plate green within a probe interval (about a second and a half), and every card recolors to a precise verdict using your real free RAM. If you Quit the app, the site falls back to the yellow plate within thirty seconds; reopening the app flips it back to green. See Local HTTP bridge for the full behaviour.

How to check the bridge from Terminal. Open Terminal (Cmd+Space, type “Terminal”, Enter) and run:

curl http://127.0.0.1:47821/health

A running bridge answers with a small JSON payload containing "ok": true and the app version. Silence, “connection refused”, or a timeout means the loopback listener is not up, which on macOS almost always means the app is being run from outside /Applications.

Why it matters

The bridge is what makes the site tell the truth about your machine. Without it, every model card falls back to a coarse browser guess that treats a 128 GB workstation and a Chromebook as the same rig, because navigator.deviceMemory caps at 8 GB. The one-time cost of running the app from Applications is what unlocks CPU model, exact RAM, and live free-memory numbers on every model page.

In Abliteration specifically

macOS clears the quarantine flag once, when the app is inside /Applications and gets launched. Subsequent launches from the Dock, from Spotlight, or from a deep link work without any extra step. A new release replaces the app in place under the same path, so quarantine is cleared again on first launch of the new version.

Catalog is the map. Apps are the tools.

Run models on your own machine, not in the cloud.

Every model page has an "Open in Abliteration" button that hands the model directly to the first-party desktop client, at the quantization your rig can actually run. No API keys, no subscription, no prompt leakage.

Get the app Browse the catalog
Open in Abliteration