Run it

Run it

Each page here is one install, recorded in order: what we ran, what came back, and how we knew it had worked.

Rows of server racks in a data centre, seen down the aisle
Photo: Hugovanmeijeren· CC BY-SA 3.0· Wikimedia Commons

What this section is for

The first hour. An installer finishes, a terminal prints something, and you are supposed to be running an agent. This section records that hour on real machines: what the installer writes to disk, which platform fails first and with which text, and how to take a backup you can actually restore. Nothing here is written from documentation alone - if we did not run it, it is not on this page.

How a page in this section is built

  • What we ran - the exact command, including the flags we gave it.
  • What came back - the output as it appeared, error text included, not paraphrased.
  • Where it diverged - the moment the machine stopped matching the instructions.
  • How we knew it worked - the check we ran afterwards, and what a pass looked like.
  • How to undo it - the files to delete or restore, known before you need them.

Pages in this section

  1. What the installer puts on disk - four directories hold state, and three of them must never leave the machine.
  2. Windows, WSL and macOS: where each one fails first - the MSYS path trap we hit, plus the parts we did not test.
  3. What to back up before an upgrade - 122 MB, 5,279 entries, and a restore verified by hash.
  4. Desktop app to a WSL backend - one JSON file decides where requests go, and the failure that looks like config is usually a stopped distro.
  5. Running it unattended - nohup and setsid both survived the shell exiting; what killed them was a shutdown, and what survives one is a unit file.
  6. The port that never opened - exposing the backend without an auth provider fails, and exits 0 while failing.

What this section does not cover

Output quality and prompt technique, API integration, billing disputes, and vendor support requests. Prices live under Cost & models; state on disk lives under Memory & tools. If a page here does not answer your question, that is worth an email - it usually means we skipped a step other people hit too.

Four checks to run before trusting any page here

Versions move. Before you follow an instruction, print what you actually have:

  • node -v - the runtime the installer and the agent both depend on.
  • wsl.exe -l -v - on Windows, whether you have a WSL distribution and which version.
  • ls -1 "$LOCALAPPDATA/hermes" | wc -l - how many top-level entries your install has already created.
  • hermes --version - the build you are comparing against.

If two of those do not match what our pages show, treat the page as a hypothesis rather than a recipe, and check the date at the top of it.