Skip to content
Hacker Blue

Docs

Install guide.

The small HackerBlue program that installs the theme you bought into your app, and keeps it up to date. You run it in your device's terminal; three steps below, every command on its own line, ready to copy.

Last updated 26 September 2026

Install a theme in three steps

From nothing to a working theme, in the order you'd do it.

Buying a theme, or claiming the free one, put the licence on your Hacker Blue account. These three steps put the theme into your app. The program behind them is the HackerBlue CLI: one small program, nothing else to install.

32 themes are installable today; the list is on the homepage.

1. Put the HackerBlue program on your device

Open Terminal (Linux or macOS) or PowerShell (Windows) and run the one line for your device. It downloads the program, checks it against the published checksum list, and puts it where you can run it; no administrator rights.

Linux or macOS: Terminal
curl -fsSL https://hackerblue.dev/install.sh | sh
Windows: PowerShell
irm https://hackerblue.dev/install.ps1 | iex

The installer puts the program in your user account, with no administrator rights. If your terminal cannot find it afterwards, the installer prints the one line to add to your PATH; on Windows it is added for you, so open a new terminal.

2. Sign in

Still in the same terminal, run this. A page opens in your browser: sign in to your Hacker Blue account and choose Approve. That allows this device to install the themes you bought, and the program finishes on its own.

Terminal
hackerblue login

No browser where you are? The command prints the address instead; open it on any device you like.

3. Install your theme

This installs the Obsidian theme:

Terminal
hackerblue install obsidian

To install the theme for a different app, put that app's address, the last part of its page, like kitty or firefox, in place of obsidian.

Then open the app and pick Hacker Blue in its theme settings (in Obsidian: Settings → Appearance → Themes).

The first time you run it

The programs are not yet signed with an Apple or Microsoft developer certificate, so your operating system may warn the first time. The installers above avoid the warning on macOS and Windows; if you download a file in a browser instead, this is what to expect:

  • macOS may say the program “cannot be opened because the developer cannot be verified”. Open System Settings → Privacy & Security and choose Open Anyway, or run xattr -d com.apple.quarantine ./hackerblue-darwin-arm64 once.
  • Windows SmartScreen may show “Windows protected your PC”. Choose More info → Run anyway.

A compiled program can still be inspected, so the protection that matters is on the server: nothing downloads without a licence, and the checksum list is what makes sure the file you run is the file that was published.

More commands

The rest of what the program can do, with its own one-line help for each.

These are for later, not for the first install. Every one runs in the same terminal, and every command that touches one app also takes --vault PATH: pass it to name that app's folder yourself, when you would rather it did not search.

Terminal
hackerblue list

“show which themes are ready and which are coming soon”; every theme, grouped ready to install and coming soon. What it prints:

Terminal
hackerblue login

“authorise this device with Hacker Blue”; the sign-in this page's step 2 runs.

Terminal
hackerblue logout

“revoke this device's authorisation”; signs this device out. Installed themes keep working, and the device slot frees at once.

Terminal
hackerblue status

“show this device's Hacker Blue state”; with no app, the account and every theme on this device; with one, that theme alone.

Terminal
hackerblue install obsidian

“install a theme you own on this device”; step 3's command. Optional [--vault PATH]. --vault names the app's folder yourself, when you would rather the program did not search.

Terminal
hackerblue update obsidian

“get the newest HackerBlue and your themes now”; with an app, only that theme is updated, to the newest published release. Optional [--vault PATH]. Updates are included with your licence, no second purchase.

Terminal
hackerblue uninstall obsidian

“remove a theme from this device and restore the previous one”; takes HackerBlue back out of the app, removing the files the install placed and putting the theme setting back the way it was. Optional [--vault PATH]. Your edits to the same config file after the install are kept. For apps with editable settings, the previous selection is recorded even when you choose the theme in the app. Browser extensions require finishing removal in the browser. If restoration fails, the installed theme and its record stay so you can try again. Your licence, your devices and your account are untouched, so you can install the theme again at any time.

Terminal
hackerblue licenses

“show third-party software notices”; also available with hackerblue --licenses or on the third-party notices page.

Updating the program

With no app, hackerblue update updates the program itself first, then every theme installed on this device:

Terminal
hackerblue update

It refuses unless the checksum list carries a valid signature from the Hacker Blue release key and the download matches its checksum; a failure leaves the running program as it was.

Direct downloads

Prefer to fetch it yourself? Each file is the whole program, and SHA256SUMS lists the SHA-256 of every one: compare with sha256sum (Linux), shasum -a 256 (macOS) or Get-FileHash (Windows), then make the file executable and put it on your PATH.

Linux, x86-64hackerblue-linux-amd64
Linux, ARM64hackerblue-linux-arm64
macOS, Intelhackerblue-darwin-amd64
macOS, Apple siliconhackerblue-darwin-arm64
Windows, x86-64hackerblue-windows-amd64.exe
Windows, ARM64hackerblue-windows-arm64.exe

Signing in, and your three devices

Signing in (hackerblue login) adds this device to your Hacker Blue account; up to three devices active at once. The page that opens in your browser shows which device is asking, its name and its system, so approve only the ones you know.

Your password is never stored by the program. The device keeps its own access key, locally; the account keeps only an unreadable fingerprint of it, enough to recognise the key, never to reuse it. A fourth device is refused with a pointer to your account page, where deactivating one frees its slot. Signing a device in again simply replaces its key.

hackerblue logout signs this device out; on the account first, then locally. The themes already installed on it keep working, and its slot frees immediately.

What install actually does

hackerblue install obsidian, hackerblue update obsidian and hackerblue uninstall obsidian are the commands that write, and each writes only the app's own theme files and the one setting that selects it. The order is fixed, and a failure at any step leaves everything exactly as it was:

  1. It finds the app: the vault or profile the app itself uses. If you have more than one and it cannot tell which, it asks rather than guesses; name one yourself with --vault PATH. If you have more than one and it cannot tell which, it asks rather than guesses; name one yourself with --vault PATH.
  2. It checks your licence first. Nothing is downloaded for an account that has not bought or claimed the theme; the command prints where to buy it, or where to claim the free one, instead.
  3. The download is checked against the checksum the release was published with, and anything unusual in it, a path escaping the folder, a symlink, is refused before a single file is written.
  4. The theme is placed with the previous version backed up first, so the app never sees a half-written theme.

A theme folder the program did not create is never replaced; it refuses and asks you to move it aside. Sibling themes and the rest of your files are never read or written.

Uninstalling takes out only HackerBlue's own change. A settings file that has not changed since the install is put back byte for byte; one you edited afterwards keeps your edits, and only HackerBlue's line or setting comes out. If a setting cannot be taken out on its own, a copy of the file is kept first and the original is restored.

Where the program keeps its files

Small files in your user account's settings. No password is ever stored, and the device's identity is a random id made on first run; not taken from your hardware.

  • device.json this device

    A name for the device and a random id. It survives signing out, so signing in again recognises the same device.

  • credentials.json access key

    This device's access key to your account, and when it was issued. Removed by hackerblue logout.

  • installs.json what is installed

    One record per installed theme; version and checksum. Written by install and update, removed by uninstall, read by status.

  • backups/ previous versions

    How a theme folder looked before an update replaced it, and a copy of a settings file before an uninstall restored it; kept outside the app's own folder. Delete old backups by hand if you want the space.

Supported platforms

Linux on x86-64 and ARM64 (one file, so it runs on any distribution), macOS on Intel and Apple silicon, and Windows on x86-64 and ARM64. Each app's settings are found the standard way on every one of them.

Troubleshooting

What the program says, and what to do about it.

command not foundThe folder the program was installed into is not on your PATH: the installer prints the line to add; on Windows open a new terminal after installing.
“cannot be opened because the developer cannot be verified” (macOS)Choose Open Anyway under System Settings → Privacy & Security, or run xattr -d com.apple.quarantine on the file once. Installing with install.sh avoids it.
“Windows protected your PC”Choose More info → Run anyway. Installing with install.ps1 avoids it.
“failed its checksum” from the installer or hackerblue updateThe download did not match the published list, so nothing was installed. Run it again; if it repeats, do not run the file.
the activation code expiredThe code is good for ten minutes. Run hackerblue login again for a new one.
“This account already has the maximum number of active devices.”Deactivate a device at your account page, then run hackerblue login again.
“no Obsidian vault was found”Name the vault yourself: hackerblue install obsidian --vault /path/to/vault.
“is not an Obsidian vault (no .obsidian folder)”The path exists but is not a vault. Open the folder in Obsidian once, or pass the vault that holds your notes.
“no JetBrains IDE was found”Start your JetBrains IDE once so it creates its folders, or point the command at it with --vault PATH.
“Codex CLI's config folder was not found”Run codex once so it creates its folder, or point the command at it with --vault PATH.
“btop's config folder was not found”Run btop once so it creates its folder, or point the command at it with --vault PATH.
“Yazi's config folder was not found”Run yazi once, or create the folder, or point the command at it with --vault PATH.
“No active licence for the Obsidian theme”The account has no licence for this theme; see Pricing. Nothing was downloaded or changed.
“failed its checksum”The download did not match the release. Nothing reached your app; run the command again.
“Hacker Blue could not be reached”status keeps showing local state; install and update refuse and change nothing. Installed themes keep working offline.
“Status Inactive” or “this device is not signed in”This device's key is no longer recognised; it may have been deactivated at your account page. Run hackerblue login again.
“This release needs hackerblue CLI X or newer”The published release asks for a newer program. Nothing was downloaded or changed.

Where to go next

Pricing lists the one-time products on sale, License sets out what a purchase lets you do, and Refund and Legal cover the rest. Managing your devices, deactivating one to free a slot, happens at your account page.