Version 0.2.0 · released 11 August 2026

Download Beacon

A keyboard-first desktop API client for macOS. Free, no account required, and everything it stores stays on your machine. Three ways in — take the first one unless you have a reason not to.

1 — Install script (recommended)

curl -fsSL https://raw.githubusercontent.com/quizuncle/beacon-releases/HEAD/install.sh | bash

One command, nothing else to decide. It downloads the correct build for your Mac, copies it to /Applications, and clears the quarantine flag, so Beacon opens straight away. It only ever fetches the DMG from this project's own GitHub releases. Read install.sh first

2 — Homebrew

brew tap quizuncle/beacon && brew install --cask beacon

For people already using brew. It picks the right build and clears the quarantine flag too, and it keeps Beacon updated alongside your other casks — brew upgrade --cask beacon.

3 — Download the DMG

Apple SiliconSHA-2566d3d607f2892…
6d3d607f2892abe80815133c8abdf62595c3e6449b768de355106bfb06dfdb92
IntelSHA-256335e355b1251…
335e355b1251365bb82d5cc379c2f5c4d4a2481d3ee9db5c3e28c5d745e5c73c

Not sure which chip you have? Apple menu → About This Mac.

All releases

The manual route: open the DMG and drag Beacon into Applications. This is the only option that needs a one-time xattr -cr /Applications/Beacon.app afterwards — here is why. The SHA-256 of each build is above if you want to verify what you downloaded.

Gatekeeper

Why macOS might say it "cannot be opened"

Apple requires a paid Developer ID — $99 a year — to notarize apps distributed outside the Mac App Store. Beacon is a free, independent project without that subscription, so macOS shows its standard warning for any unsigned app from the internet: "Beacon.app is damaged and can't be opened" or "cannot be opened because the developer cannot be verified." The app is not damaged; that is just what macOS says about anything unsigned.

Most people never see this. Both the install script and Homebrew clear the quarantine flag as part of installing, so Beacon opens normally the first time. If you used either of those, there is nothing to do here.

The manual DMG route is the one that hits it, because dragging an app out of a disk image leaves macOS's quarantine attribute attached. Run this once in Terminal after dragging Beacon into Applications:

Only needed after a manual DMG install

xattr -cr /Applications/Beacon.app

Then open Beacon normally. You will not need to do it again for this version. As an alternative without Terminal: right-click Beacon.appOpenOpen in the dialog that appears, which bypasses Gatekeeper for that one launch.

xattr -cr removes the quarantine attribute macOS attaches to downloaded files. It does not disable any security check — it tells macOS "I have reviewed this and trust it," which is exactly what the right-click-Open flow does through the UI.

Requirements

What you need

  • macOS 12 (Monterey) or later.
  • Apple Silicon or Intel — both are published with every release, and both the install script and Homebrew detect which you have. You only need to know if you are picking a DMG by hand: on the About This Mac panel, anything listed as an M-series chip is Apple Silicon; anything listed as an Intel Core is not.
  • macOS only. There are no Windows or Linux builds, and no committed date for other platforms yet.

Updating

Staying current

Beacon checks for updates at most once an hour: shortly after launch if it has not checked in the last hour, and then hourly while it keeps running. When a newer version exists, a toast appears in the bottom-right reading "Beacon <version> is available" with the release notes underneath — expand What's new to read what changed before deciding. Download & Install does the rest, then leaves you a Restart to finish button to press when you are ready — Beacon never restarts itself out from under you. Dismiss the toast to deal with it later; Settings → General → Check for Updates runs a check on demand.

If you installed through Homebrew, you can also upgrade from the terminal:

Homebrew upgrade

brew upgrade --cask beacon

Uninstall

Removing it again

Read this first: the second command's ~/Library/Application Support/beacon path is your local SQLite database — collections, requests, environments, history, cookies, flows, monitors and settings. Removing it deletes all of that permanently, with no hosted backup to restore from. Export anything you want to keep before you run it. Homebrew leaves that directory in place unless you add --zap, so the first command on its own is non-destructive.

Homebrew installs

brew uninstall --cask beacon

Manual installs — deletes your local data

rm -rf /Applications/Beacon.app ~/Library/Application\ Support/beacon ~/Library/Preferences/com.vivek.beacon.plist ~/Library/Saved\ Application\ State/com.vivek.beacon.savedState

Version check

Is this page current?

This page is built from release v0.2.0, published 11 August 2026. Nothing on this site talks to GitHub on its own — press the button and it will ask, once.

Every build, with its checksums.

Past releases, their notes, and the SHA-256 of every DMG live on GitHub.