Skip to content

Hermes Console Setup v1.5.0

Choose a tag to compare

@xP3ta xP3ta released this 11 Sep 02:29
· 16 commits to main since this release

Installer for connecting a self-hosted Hermes Agent to Hermes Console. This release is validated on Windows, Unix and macOS.

Install

Windows -- PowerShell 5.1+ as Administrator:

irm https://raw.githubusercontent.com/xP3ta/hermes-setup/main/hermes-mobile-setup.ps1 | iex

Linux / macOS / Termux:

curl -fsSL https://raw.githubusercontent.com/xP3ta/hermes-setup/main/hermes-mobile-setup.sh | sh

For a frozen, hash-verifiable revision, replace main with setup-v1.5.0.

What changed

A branded install experience, on Windows and Unix alike:

  • An ASCII product banner and a live progress bar with a percentage per phase, so a slow first start is visible instead of looking stuck.
  • The percentage never comes from a clock. It advances with completed phases, and the two slow phases (installing Hermes Agent, building the Dashboard) show real activity -- the owning task still running, the service log still growing -- without claiming progress that cannot be proven.
  • Nothing changes when the output is not a terminal: logs and CI keep the previous plain format byte for byte.
  • Windows now prints the pairing result in the console, like Unix already did: the QR in ASCII, the hermes://pair?... link and the image path. Previously Windows only wrote a PNG file, so it was easy to finish an install and see no code to scan.
  • The link and the QR are printed to the console only: they are never written to the audit log or a support bundle. The ASCII render is read from its own file rather than the captured stdout, so no token can leak into a log you share.

Everything from the previous release is still here: service port overrides, the progress-driven Dashboard readiness wait, phone-facing address candidates, -Uninstall / -Uninstall -Purge, the -Diagnose hint on every bounded failure, and Mobile Bridge 1.18.1 verified against a closed manifest before anything runs.

Validated on

  • Windows 10/11 and Windows Server: full install, rerun, rollback, custom ports and uninstall; reviewer suite 297 checks, zero skips, under Windows PowerShell 5.1 and PowerShell 7.
  • Debian with systemd: full install, idempotent rerun, authenticated probes; contract suite 36 checks.
  • macOS (Apple Silicon): BSD /bin/sh syntax, a real launchctl service lifecycle, and a full isolated install whose three services answer authenticated probes while a protected route rejects an anonymous request.

Not validated natively: Intel macOS, Linux ARM64/Termux, Windows ARM64, and a public HTTPS deployment behind a reverse-proxy certificate.

Notes

  • Setup is plain, auditable source -- read it before running.
  • No telemetry and no hosted relay.
  • No installer binaries are attached: the source is the truth, which is what makes the installed bytes verifiable by hash.