Hermes Agent

Getting started with Hermes Agent

A practical sequence: install with the upstream script, run the setup wizard, pick a model, then optionally bring up the messaging gateway. Always read the official security page before exposing bots to the internet.

Last updated: 2026-04-19 Hermes hub Hermes vs OpenClaw

Disclaimer

Commands below are copied from the public Hermes Agent README as of 2026-04-19. Verify on GitHub before running; GPT54Prompts is not affiliated with Nous Research.

1. Prerequisites

  • Linux, macOS, WSL2, or Android (Termux): supported by the official installer per README.
  • Windows (native): not supported; use WSL2 and run the Linux install there.
  • API keys for whichever model provider you choose (see hermes model after install).

2. Install

From the upstream README:

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

Reload your shell, then start the CLI:

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

Termux has a documented manual path in the official docs; the README notes Android-specific dependency caveats for the full .[all] extra.

3. First-time configuration

Run the full wizard (configures models, tools, gateway-related settings in one flow):

hermes setup

If you are migrating from OpenClaw, upstream says hermes setup can detect ~/.openclaw and offer migration before configuration. You can also run hermes claw migrate anytime (see comparison page).

4. Everyday commands (cheat sheet)

These entry points are documented in the README:

  • hermes — interactive terminal UI
  • hermes model — provider and model selection
  • hermes tools — enable or disable tools
  • hermes config set — individual config keys
  • hermes gateway — messaging gateway (after setup)
  • hermes doctor — diagnostics
  • hermes update — upgrade

5. Messaging gateway (outline)

To talk to Hermes from Telegram, Discord, Slack, WhatsApp, Signal, or email, the README points to gateway setup and start:

hermes gateway setup
hermes gateway start

Pairing, allowlists, and command approval are security-sensitive. Follow Messaging Gateway and Security on the official site.

6. Safety checklist

  • Treat inbound DMs as untrusted input; lock down who can talk to your bot.
  • Understand which tools can read, write, or execute on your host (or container backend).
  • Run hermes doctor after config changes.
  • Prefer starting on a non-production machine until you understand gateway pairing.

7. Developers (optional)

Contributors clone the repo and use setup-hermes.sh or uv as documented in the README. That path is separate from the end-user installer above.