Repository navigation
Releases
Hermes Console Setup v1.5.2
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 | iexLinux / macOS / Termux:
curl -fsSL https://raw.githubusercontent.com/xP3ta/hermes-setup/main/hermes-mobile-setup.sh | shReplace main with setup-v1.5.2 for a frozen, hash-verifiable revision.
What changed
Windows: pairing could be silently broken by a dismissed firewall prompt.
Windows creates inbound block rules for an executable when the "allow this app
on private/public networks?" dialog is dismissed. Block rules win over allow rules,
so the services kept listening, setup reported every check as passed, and no other
device on the network could reach the phone-facing ports -- an install that looked
perfect and could never pair.
Setup now:
- creates the firewall permissions (port rules and per-application rules) before
any service starts listening, because the prompt appears at that exact moment; - removes the enabled inbound block rules that cover the managed executables (only
those, and only the programs it manages), since an allow rule cannot outrank them.
If your previous install was in that state, running this revision repairs it: the
block rules are cleared and the application rules are added without touching the
verified port rule.
Everything from v1.5.1 and v1.5.0 is included: branded banner and progress bar on
Windows and Unix, the pairing result (ASCII QR, link and image path) in the console,
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 319 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/shsyntax, a reallaunchctlservice 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.
Hermes Console Setup v1.5.1
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 | iexLinux / macOS / Termux:
curl -fsSL https://raw.githubusercontent.com/xP3ta/hermes-setup/main/hermes-mobile-setup.sh | shReplace 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/shsyntax, a reallaunchctlservice 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.
Hermes Console Setup v1.5.0
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 | iexLinux / macOS / Termux:
curl -fsSL https://raw.githubusercontent.com/xP3ta/hermes-setup/main/hermes-mobile-setup.sh | shFor 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/shsyntax, a reallaunchctlservice 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.
Hermes Console Setup v1.4.0
One-command installer that connects a self-hosted Hermes Agent to Hermes Console. This is the revision validated on Windows, Unix and macOS.
Install
Windows -- PowerShell 5.1+ as Administrator:
irm https://raw.githubusercontent.com/xP3ta/hermes-setup/setup-v1.4.0/hermes-mobile-setup.ps1 -OutFile "$env:TEMP\hermes-setup.ps1"
& "$env:TEMP\hermes-setup.ps1"Linux / macOS / Termux:
curl -fsSL https://raw.githubusercontent.com/xP3ta/hermes-setup/setup-v1.4.0/hermes-mobile-setup.sh | shWhat changed
Windows and Unix
- Service ports can be moved with
HERMES_GATEWAY_PORT,HERMES_DASHBOARD_PORTandHERMES_BRIDGE_PORT. Defaults are unchanged (8642 / 9119 / 9131). An invalid, out-of-range or duplicated value stops the run before anything is modified, so a port owned by another process no longer forces you to kill it. - Dashboard readiness now extends while the Dashboard is really building (its task still running, or its log still growing), up to 30 minutes, with an explicit trail in the log. It fails bounded when nothing progresses, so a real failure cannot hide behind a long wait.
- Pairing probes up to three candidate addresses and adopts the one that actually answers, re-verifying the firewall rule when the address kind changes. A machine with a VPN, Hyper-V/WSL adapters or a second NIC no longer fails with an address the phone cannot reach.
Windows
-Uninstalland-Uninstall -Purge: removes only what the installer created (its own Scheduled Tasks, its own firewall rules and the pairing artifacts) and is idempotent.-Purgealso removes the Hermes home, and refuses a path that is not a recognisable Console home.- Every bounded failure now points at
-Diagnose, which writes a redacted report — no tokens, API keys or pairing credentials.
macOS
- Fixed: the installer did not parse under the system
/bin/sh(bash 3.2). - Fixed: the service runners could not find Node/npm, because launchd does not inherit the session
PATH, so the Dashboard never started and the install failed. - Linux-only contract checks are now skipped with a reason on other platforms instead of being reported as failures.
Mobile Bridge -- unchanged in this release: 1.18.1. Its download is verified against a closed manifest (size, SHA-256 and source version) before anything runs.
Validated on
- Windows 10/11 and Windows Server: full install, rerun, rollback, custom ports and uninstall; reviewer suite 275 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/shsyntax, a reallaunchctlservice 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 to this release: the tag is the source of truth, which is what makes the installed bytes verifiable by hash.