Academy · Terminal agents · TA-05

TA-05 · Optional · open multi-provider

Hermes Agent

Install the real Hermes (Nous Research agent), not a name-collision project — then configure and chat once.

45–75 min · same day Needs: TA-01 + provider path Outcome: configured hermes — or honest skip

Who this is for

People who want an open, multi-provider terminal agent — not single-lab lock-in. Hermes has more knobs than Claude Code or Codex; if you want the simplest path, you already have it.

Which “Hermes”? Read this first

CandidateWhat it isTerminal agent?
Nous Research Hermes AgentOpen agent with CLI/TUI, tools, gateway — hermes-agent.nousresearch.comYes — this module
“Hermes” LLM / model brandsModels, not a full installable agent productNo (models ≠ CLI)
Unrelated Hermes protocols / crypto / reposName collisionNo

Which machine are you on? (saved from TA-01 if you picked there)

↑ Pick one to see only your install path. (Showing all until you do.)

The emergency brake

  • Installer hangs or scrolls forever? Hold Ctrl + tap C, close the terminal, open a fresh one, try once more.
  • Scary red text? Copy the exact error — you'll need it for the fix table below or a consult. Red text is information, not damage.

OS matrix — pick your row

Compare all three OS paths (reference — your picker above already filtered the steps)
macOSWindows nativeWSL
CLI installcurl -fsSL https://hermes-agent.nousresearch.com/install.sh | bashiex (irm https://hermes-agent.nousresearch.com/install.ps1)Same curl installer as Linux
Desktop (optional)DMG from site — Apple Silicon only.appinstaller / MSIX from sitePrefer CLI inside WSL
After installsource ~/.zshrc → hermesNew PowerShell windowsource ~/.bashrc → hermes
installmacOS / WSL 
curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash
installWindows PowerShell 
iex (irm https://hermes-agent.nousresearch.com/install.ps1)

Install, verify, and run once

  1. Run the CLI installer for your OS (Desktop optional).
  2. Reload shell → hermes or hermes --tui.
  3. Configure provider: hermes setup --portal (fast path) or hermes model / hermes setup.
  4. First run: ask a question about the current directory.
  5. Diagnostics: hermes doctor if anything's missing.

Try this

Run the version check for your OS path right now — before the login step.

You should see: a version number. command not found instead? Close the terminal, open a fresh window, and try once more — PATH usually fixes itself.

Undo: wrong install? Re-run your OS block in a fresh terminal. Nothing here deletes files.

Docs: Installation · Quickstart.

Success check

  • hermes launches (CLI or TUI)
  • Provider/model configured via portal or hermes model
  • One chat about the current directory works

Common failure modes

FailureFix
hermes: command not foundReload shell; ensure ~/.local/bin (or Windows Hermes bin) is on PATH
API key not sethermes model or portal setup — don't paste keys into random chats
Intel Mac + DesktopDesktop not supported on Intel — CLI installer only
Installed the wrong “Hermes”Re-read the ambiguity table; uninstall the wrong tool

Don't buy / don't install yet

Skip Hermes if you already have one lab CLI working and don't want another config surface. Skip paying for multiple providers “to unlock Hermes” before you've run hermes doctor once.

Commands checked 2026-09-25 against Nous Research docs; if one fails, the official page wins.

Config knobs multiplying?

Hermes rewards one focused setup session. Bring hermes doctor output and we'll read it together.

Book free