DOWNLOAD / INSTALL HM
One binary. Three commands, or the app.
hm is a single command-line program. It runs on your machine, against a folder on your machine that holds the project and its record — a Works. The macOS application is the same program with a window around it. Installing either creates no account and moves none of your work.
01 / ACCESS
Access is limited, and it comes first.
Every path below authenticates against a private repository, so a working install starts with read access to it. Without that, the commands return a not-found error rather than a binary, which is a failure worth naming before you run one.
Access is granted per person, and the request route is the contact page. If you cannot reach it, ask whoever pointed you at this page.
02 / PLATFORMS
What a release publishes.
A tagged release produces one archive for each target below, with the hm binary at its root: hm-0.1.38-{target}.tar.gz. Apple silicon gets a second artifact, which is the desktop application in a disk image: hm_0.1.38_aarch64.dmg. The last column is what the release named above it has on its page — a target the profile names and the job does not build says so, and so does an artifact this release was cut too early to carry.
| Machine | Target | v0.1.38 |
|---|---|---|
| macOS · Apple silicon | aarch64-apple-darwin | Published |
| Linux · x86-64 | x86_64-unknown-linux-gnu | Published |
| macOS · Intel | x86_64-apple-darwin | Not built yet |
| Linux · arm64 | aarch64-unknown-linux-gnu | Not built yet |
| macOS · Apple silicon · the app | aarch64-apple-darwin | Published |
03 / INSTALL
Three commands for the binary on its own.
The first is the shortest, the second is the one to reach for when you already live in the terminal, and the third builds from source. All three end with the same program at version 0.1.38.
01 / The install script
A token with repo scope. Puts hm in ~/.local/bin, and re-running it replaces the binary in place.
export GITHUB_TOKEN="$(gh auth token)" curl -fsSL -H "Authorization: Bearer $GITHUB_TOKEN" \ https://raw.githubusercontent.com/hyrumai/hyrum-machinery/main/scripts/install.sh | bash02 / The GitHub CLI
The gh command, signed in. Swap the triple for the one your machine matches in the table above.
gh auth login gh release download v0.1.38 --repo hyrumai/hyrum-machinery \ --pattern 'hm-*-aarch64-apple-darwin.tar.gz' --dir /tmp/hm-dl tar -xzf /tmp/hm-dl/hm-*.tar.gz -C ~/.local/bin03 / The source build
A Rust toolchain at 1.74 or newer, and credentials for the repository. The binary lands in ~/.cargo/bin.
cargo install --git https://github.com/hyrumai/hyrum-machinery.git \ --tag v0.1.38 \ --path crates/hm-cli \ --features pilot-executors \ --locked
Then check it
The version the binary prints is the tag it was cut from, with the v dropped.
hm --version
# 0.1.3804 / THE DESKTOP
The workbench is a macOS application.
The board you direct work from is an app — Apple silicon, macOS 11 or later, and a window over the same hm the commands above install. It carries its own copy of that binary inside the bundle, so it needs no install before it and leaves an hm you already have alone.
It is published beside the archives on the release page for v0.1.38, and that release’s own SHA256SUMS covers it.
The image — hm_0.1.38_aarch64.dmg — is read off the release page rather than reached from a button here. It is named for the version it was cut from, and the repository is private, so an address to the file itself would be a link that goes stale on the next release and 404s for anyone who is not signed in. Access is the same access the commands need. The release page
The application is unsigned, and that costs one detour on first open: macOS refuses a copy that arrived through a browser, and the way past it is System Settings → Privacy & Security → Open Anyway, once per copy. The walkthrough is the macOS section of docs/runbooks/install.md in the repository. Signing and notarization are not scheduled.
05 / WHAT CHANGED
Each release says what moved.
v0.1.38 is the tag this page publishes, and the same number is what hm --version prints once it is installed. What each release changed is kept in the changelog.