# Test Builds Every push to `dev` runs the [Test builds](https://github.com/anomalyco/hex/actions/workflows/test-builds.yml) 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. ```ts hex-test--macos-arm64 // hex-test--arm64.dmg hex-test--windows-x86_64 // hex-setup--windows-x64.exe + bare hex--windows-x64.exe hex-test--windows-aarch64 // hex-setup--windows-arm64.exe + bare hex--windows-arm64.exe hex-test--linux-x86_64 // hex--linux-x64 ``` None 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. ## macOS (Apple silicon, macOS 15 or later) 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. 1. Quit Hex from its menu-bar icon. 2. Open the DMG and drag **Hex Test** to Applications. 3. Clear the download quarantine, which macOS otherwise reports as an app that cannot be opened or is damaged: ```sh xattr -dr com.apple.quarantine "/Applications/Hex Test.app" ``` Alternatively, open it once, then choose **Open Anyway** in System Settings → Privacy & Security. 4. 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. ## Windows (10 or 11, x64 or ARM64) The installer and executable are unsigned, so SmartScreen warns: choose **More info**, then **Run anyway**. Smart App Control is stricter: it blocks an unsigned setup engine, and turning it off cannot be fully undone without resetting Windows. Use a VM, or a machine where it is already off; release installers carry the signed engine and work with it on. 1. Quit Hex from its tray icon. 2. Run `hex-setup--windows-.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 bare `hex--windows-.exe` from any folder. 3. The test build never self-updates. To return to the release, run the release installer from . ## Linux (x86_64) 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: ```sh 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 window ``` After Ctrl-C, `hex` starts the installed Hex again. ## Reporting Include the commit from the artifact name, the OS and architecture, and the logs: `~/Library/Application Support/hex/logs/` on macOS, `%LOCALAPPDATA%\hex\logs\` on Windows, and `~/.local/share/hex/logs/` on Linux.