Install Hermes Agent

This page is about setup. If your question is "what should I do on my first run?", go to Get started with Hermes Agent.

Start with the official installer

For most people, the best installation path is the official one-line installer:

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

That is the official quick install path for Linux, macOS, and WSL2. Native Windows is not the target runtime today, so the practical Windows path is to install WSL2 first and run Hermes inside that environment.

What you need before installation

The current official install path is intentionally light on prerequisites:

• git is the only required prerequisite for the one-line installer
• Linux, macOS, or WSL2 is the supported starting point
• a terminal-first workflow is the right mindset for the first run
• you will also need an LLM provider account or endpoint when you configure Hermes after installation

If you are evaluating Hermes for the first time, local installation is the right default. It keeps the first run simple and lets you understand the runtime model before you add Docker or server operations.

Can you install Hermes Agent on Windows?

Not as a native-first path today. The practical Windows route is WSL2, then Hermes inside that Linux environment. That is the closest thing to an official Windows answer right now, and it matches how Hermes is actually meant to run.

Is Hermes Agent a good fit for Ubuntu?

Yes. Ubuntu and similar Linux environments are a natural fit for Hermes because the official install and CLI workflow are built around a terminal-first Linux-friendly runtime.

What the installer actually does

According to the official docs, the installer handles the repo clone, virtual environment, global hermes command setup, provider configuration flow, and the main runtime dependencies Hermes expects. That includes Python, Node.js, ripgrep, and ffmpeg.

In practice, that means the installer is trying to get you to a usable terminal session fast, not just copy files onto your machine.

After installation

When the installer finishes, reload your shell and verify that the CLI starts:

source ~/.bashrc   # or source ~/.zshrc
hermes

If hermes launches, you have crossed the main setup boundary. The next questions are usually:

• which provider and model should Hermes use?
• which tools should be enabled?
• what should the first real task be?

Those are covered in Get started with Hermes Agent.

The key setup commands to know

The official docs point new users to these commands after install:

hermes model       # choose your provider and model
hermes tools       # configure available tools
hermes setup       # run the full setup wizard

You do not need to master every command before the first run. The practical sequence is:

1. install Hermes
2. choose a provider with hermes model or use hermes setup
3. start the CLI with hermes
4. give it one small real task

When local install is enough

Local install is usually the right starting point when you want:

• the fastest first run
• the least infrastructure overhead
• a real feel for the terminal workflow
• proof that Hermes fits your environment before you add more complexity

For a first evaluation, this is usually the best tradeoff.

When you might move beyond local

You do not need Docker or VPS on day one. Move only when the need becomes real.

Move to Docker when

• you want a cleaner runtime boundary
• you care about reproducibility across machines
• you want a controlled bridge between local evaluation and a longer-lived environment

Move to VPS or cloud when

• Hermes should stay online continuously
• it needs to live closer to services, automations, or messaging integrations
• you are now optimizing for runtime shape, not just first-time setup

If that is already your situation, use Deploy after installation.

If you want full manual control

The official installation docs also document a manual path:

• clone the repo with submodules
• install uv
• create a Python 3.11 virtual environment
• install Hermes and any optional extras
• install Node.js dependencies only when you need browser automation or the WhatsApp bridge

That path is useful when you want to understand every moving part or customize the environment yourself. For most users, it is not the best first step.

Use the official installation guide for the full manual flow.

What to do next

• Read Get started with Hermes Agent if installation is done and you want the first real run
• Read Deploy if you already know Hermes should move beyond local setup
• Read What is Hermes Agent? if you still want a clearer mental model before you use it

Hermes Agent installation FAQ

Is local install the best first step?

Yes for most new users. It is the fastest path to understanding Hermes without adding Docker or server complexity too early.

Does the installer handle dependencies for me?

Yes. The official installer is designed to handle the main runtime dependencies and leave you with a working hermes command, not just a cloned repository.

Do I need Docker to install Hermes Agent?

No. Docker is optional and usually makes more sense after you already understand the local runtime.

Can you install Hermes Agent on Windows?

Yes through WSL2, which is the practical Windows path today. Native Windows should not be treated as the primary first-run environment.

Does Hermes Agent run well on Ubuntu?

Yes. Ubuntu is one of the most natural environments for Hermes because the official install and CLI flow are built around Linux-style terminal workflows.

Can I install Hermes locally and move to Docker or VPS later?

Yes. That is the most natural path for many users: local first, then Docker for cleaner reproducibility, then VPS or cloud when Hermes should stay online.

Where should I look if I want the authoritative install steps?

Use the official installation docs.