Installation & Quickstart: Official Setup Flow

Installation is only the first checkpoint

The docs recommend the same installer for Linux, macOS, WSL2, and Android / Termux. That shared installer matters because it collapses the first decision, but it does not remove the need to choose a clean platform path.

curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh | bash

Platform guidance

• Native Windows is not the supported path; official docs direct users to WSL2
• Termux is officially documented and supported by the installer flow

Minimal preflight checklist

• Use a supported shell environment you are willing to keep for follow-up steps
• Make sure Git is available before you start
• Pick one provider path for the first run instead of researching every option at once
• Decide whether your goal is local terminal use, remote messaging access, or migration from an older setup

What experienced operators should do next

source ~/.bashrc
hermes
hermes setup
hermes gateway setup
hermes gateway

The key thing to avoid is treating install completion as success. The real success point is a completed hermes setup run with one provider path that works cleanly in the terminal.

What usually goes wrong in the first install

• Users confuse "installer finished" with "Hermes is configured"
• Users branch into Telegram, MCP, and multiple providers before the CLI path works
• Users on Windows lose time trying native installs instead of moving straight to WSL2

What a successful first run actually looks like

1. hermes starts cleanly
2. hermes setup finishes with one provider path you understand
3. You can ask for one small real task and get a stable response
4. Only then do you branch into gateway, migration, or MCP

Better default after install

Finish one clean terminal flow first. After that, choose exactly one branch: remote access, migration, provider comparison, or tool integration. That is the easiest way to keep the first session useful instead of sprawling.

Operator takeaway

Good installation guidance is not about worshipping the install command. It is about reducing decision noise so that the first working session tells you something real. If your first hour with Hermes ends with one clean terminal path and one clear next branch, the setup is doing its job.