Skip to content

Hermes Console Setup v1.5.1

Choose a tag to compare

@xP3ta xP3ta released this 11 Sep 03:25
· 14 commits to main since this release

Installer for connecting a self-hosted Hermes Agent to Hermes Console. 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

Replace main with setup-v1.5.1 for a frozen, hash-verifiable revision.

What changed

Windows: no more Windows Firewall prompt. A clean install could still show the
dialog "allow this app on private/public networks?" even though setup had already
created a rule for the three service ports, because Windows asks per application
when an executable starts listening.

That dialog is not cosmetic: if it is dismissed, Windows adds a block rule and the
phone can never pair, while every check the installer runs still passes -- and the
installer promises no dialogs.

Setup now also creates inbound allow rules scoped to the managed executables (the
Hermes virtual-environment interpreter and launcher) with the same private-LAN or
Tailscale remote scope, the same three ports and their own display name, so Windows
has nothing to ask. They are created idempotently, so an existing install gets them
on the next run without touching the verified port rule, and they are registered in
the transaction so a rollback removes them.

Everything from v1.5.0 is unchanged: the branded banner, the progress bar with
honest per-phase percentages, the pairing result (ASCII QR, link and image path)
printed in the console on Windows and Unix, service port overrides, the
progress-driven Dashboard readiness wait, phone-facing address candidates and
-Uninstall / -Uninstall -Purge.

Validated on

  • Windows 10/11 and Windows Server: full install, rerun, rollback, custom ports and uninstall; reviewer suite 310 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.