Every push to dev runs the Test builds
workflow (.github/workflows/test-builds.yml; run it by hand with Run
workflow). Open the latest green run: its summary links each download.
Artifacts are kept 14 days, and downloading one requires a GitHub login with
access to the repository.
hex-test-<commit>-macos-arm64 // Hex-Test-<commit>-arm64.dmg
hex-test-<commit>-windows-x86_64 // Hex-Setup-<version>-windows-x64.exe + bare Hex-<version>-windows-x64.exe
hex-test-<commit>-windows-aarch64 // Hex-Setup-<version>-windows-arm64.exe + bare Hex-<version>-windows-arm64.exe
hex-test-<commit>-linux-x86_64 // hex-<version>-linux-x64None of these are code-signed, notarized, or published. They never update themselves, so the signed release cannot replace the build you are testing. GitHub wraps each artifact in a zip; unzip it first.
The test app is Hex Test.app (bundle ID anomaly.hex.test),
ad-hoc signed and never checks for updates. Its own name and bundle ID let it sit
beside a released Hex.app without touching that app's permissions, login
item, or updates. It also keeps its own data: settings, models, History, and
meetings live in ~/Library/Application Support/hex-test, personal commands in
~/.config/hex-test, and meeting Markdown in ~/Documents/Hex Test Meetings,
so it starts with onboarding and never reads or changes the installed Hex's
data. Both apps listen to the same shortcut and microphone, so run one at a
time.
-
Quit Hex from its menu-bar icon.
-
Open the DMG and drag Hex Test to Applications.
-
Clear the download quarantine, which macOS otherwise reports as an app that cannot be opened or is damaged:
xattr -dr com.apple.quarantine "/Applications/Hex Test.app"Alternatively, open it once, then choose Open Anyway in System Settings → Privacy & Security.
-
Open Hex Test and grant Microphone and Accessibility again. Ad-hoc signatures change with every build, so each new test build needs these grants again: remove the old Hex Test entries in System Settings and add the new app.
To go back, quit Hex Test, delete it, and open Hex.
The installer and executable are unsigned, so SmartScreen warns: choose More info, then Run anyway.
- Quit Hex from its tray icon.
- Run
Hex-Setup-<version>-windows-<x64|arm64>.exe. It replaces an installed Hex of the same or an older version in the usual per-user layout, and refuses to replace a newer one: uninstall that first from Apps & Features (settings are kept). Or skip the installer and run the bareHex-<version>-windows-<arch>.exefrom any folder. - The test build never self-updates. To return to the release, run the release installer from https://anoma.ly/hex.
An installed Hex starts through its systemd user unit, so launching the test binary normally would just start the installed one. Run the test binary as the instance directly instead:
hex quit
chmod +x hex-*-linux-x64
./hex-*-linux-x64 service # runs Hex in the foreground; Ctrl-C quits
./hex-*-linux-x64 # in another terminal: opens the windowAfter Ctrl-C, hex starts the installed Hex again.
Include the commit from the artifact name, the OS and architecture, and the
logs: ~/Library/Application Support/hex/logs/ on macOS,
%APPDATA%\hex\logs\ on Windows, and
~/.local/share/hex/logs/ on Linux.