FAQ Hermes Agent

FAQ Hermes Agent

Cette page fait partie du guide pratique francophone consacré à Hermes Agent. Elle répond à l'intention de recherche : répondre aux questions fréquentes.

Le contenu s'appuie sur la documentation officielle Hermes Agent associée à cette page. L'objectif n'est pas de remplacer la documentation de Nous Research, mais de fournir une lecture claire en français, structurée pour aller vite, avec un maillage logique vers les pages complémentaires du même site.

À retenir

  • Sujet principal : faq hermes agent.
  • Type de page : hub.
  • Cluster : support.
  • Source canonique : documentation officielle Hermes Agent.
  • Aucun lien vers l'autre domaine n'est utilisé dans cette page.

Comment utiliser cette section

Cette section regroupe les pages du cluster support. Commencez par cette page si vous voulez comprendre le sujet dans son ensemble, puis ouvrez les guides détaillés selon votre contexte.

Chaque page interne contient des liens vers les prérequis, les pages voisines et les suites logiques. Le but est de créer un parcours utile, pas une liste brute de pages SEO.

Base officielle

Quick answers and fixes for the most common questions and issues.

---

Frequently Asked Questions

What LLM providers work with Hermes?

Hermes Agent works with any OpenAI-compatible API. Supported providers include:

  • OpenRouter — access hundreds of models through one API key (recommended for flexibility)
  • Nous Portal — Nous Research's subscription gateway — 300+ models plus web/image/TTS/browser through one OAuth login (recommended for newcomers)
  • OpenAI — GPT-5.4, GPT-5-codex, GPT-4.1, GPT-4o, etc.
  • Anthropic — Claude models (direct API, OAuth via hermes auth add anthropic, OpenRouter, or any compatible proxy)
  • Google — Gemini models (direct API via gemini provider, OpenRouter, or compatible proxy)
  • z.ai / ZhipuAI — GLM models
  • Kimi / Moonshot AI — Kimi models
  • MiniMax — global and China endpoints
  • Local models — via Ollama, vLLM, llama.cpp, SGLang, or any OpenAI-compatible server

Set your provider with hermes model or by editing ~/.hermes/.env. See the Environment Variables reference for all provider keys.

Does it work on Windows/Android/Termux/my plataform??

See Platform Support for the full platform availability matrix.

I run Hermes in WSL2. What's the best way to control my normal Windows Chrome?

Prefer an MCP bridge over /browser connect.

Recommended pattern:

  • run Hermes inside WSL2
  • keep using your normal signed-in Chrome on Windows
  • add chrome-devtools-mcp as an MCP server through cmd.exe or powershell.exe
  • let Hermes use the resulting MCP browser tools

This is more reliable than trying to force Hermes core browser transport to attach directly across the WSL2/Windows boundary.

See:

  • Use MCP with Hermes
  • Browser Automation

Is my data sent anywhere?

API calls go only to the LLM provider you configure (e.g., OpenRouter, your local Ollama instance). Hermes Agent does not collect telemetry, usage data, or analytics. Your conversations, memory, and skills are stored locally in ~/.hermes/.

Can I use it offline / with local models?

Yes. Run hermes model, select Custom endpoint, and enter your server's URL:

hermes model

Or configure it directly in config.yaml:

model:
  default: qwen3.5:27b
  provider: custom
  base_url: http://localhost:11434/v1

Hermes persists the endpoint, provider, and base URL in config.yaml so it survives restarts. If your local server has exactly one model loaded, /model custom auto-detects it. You can also set provider: custom in config.yaml — it's a first-class provider, not an alias for anything else.

This works with Ollama, vLLM, llama.cpp server, SGLang, LocalAI, and others. See the Configuration guide for details.

If you set a custom num_ctx in Ollama (e.g., ollama run --num_ctx 64000), make sure to set the matching context length in Hermes — Ollama's /api/show reports the model's *maximum* context, not the effective num_ctx you configured.

Hermes auto-detects local endpoints and relaxes streaming timeouts (read timeout raised from 120s to 1800s, stale stream detection disabled). If you still hit timeouts on very large contexts, set HERMES_STREAM_READ_TIMEOUT=1800 in your .env. See the Local LLM guide for details.

How much does it cost?

Hermes Agent itself is free and open-source (MIT license). You pay only for the LLM API usage from your chosen provider. Local models are completely free to run.

Can multiple people use one instance?

Yes. The messaging gateway lets multiple users interact with the same Hermes Agent instance via Telegram, Discord, Slack, WhatsApp, or Home Assistant. Access is controlled through allowlists (specific user IDs) and DM pairing (first user to message claims access).

What's the difference between memory and skills?

  • Memory stores facts — things the agent knows about you, your projects, and preferences. Memories are retrieved automatically based on relevance.
  • Skills store procedures — step-by-step instructions for how to do things. Skills are recalled when the agent encounters a similar task.

Both persist across sessions. See Memory and Skills for details.

Can I use it in my own Python project?

Yes. Import the AIAgent class and use Hermes programmatically:

from run_agent import AIAgent

agent = AIAgent(model="anthropic/claude-opus-4.7")
response = agent.chat("Explain quantum computing briefly")

See the Python Library guide for full API usage.

---

Troubleshooting

Installation Issues

hermes: command not found after installation

Cause: Your shell hasn't reloaded the updated PATH.

Solution:

source ~/.bashrc    # bash
source ~/.zshrc     # zsh

If it still doesn't work, verify the install location:

which hermes
ls ~/.local/bin/hermes

The installer adds ~/.local/bin to your PATH. If you use a non-standard shell config, add export PATH="$HOME/.local/bin:$PATH" manually.

Python version too old

Cause: Hermes requires Python 3.11 or newer.

Solution:

python3 --version   # Check current version

sudo apt install python3.12   # Ubuntu/Debian
brew install python@3.12      # macOS

The installer handles this automatically — if you see this error during manual installation, upgrade Python first.

Terminal commands say node: command not found (or nvm, pyenv, asdf, …)

Cause: Hermes builds a per-session environment snapshot by running bash -l once at startup. A bash login shell reads /etc/profile, ~/.bash_profile, and ~/.profile, but does not source ~/.bashrc — so tools that install themselves there (nvm, asdf, pyenv, cargo, custom PATH exports) stay invisible to the snapshot. This most commonly happens when Hermes runs under systemd or in a minimal shell where nothing has pre-loaded the interactive shell profile.

Solution: Hermes auto-sources ~/.bashrc by default. If that's not enough — e.g. you're a zsh user whose PATH lives in ~/.zshrc, or you init nvm from a standalone file — list the extra files to source in ~/.hermes/config.yaml:

terminal:
  shell_init_files:
    - ~/.zshrc                     # zsh users: pulls zsh-managed PATH into the bash snapshot
    - ~/.nvm/nvm.sh                # direct nvm init (works regardless of shell)
    - /etc/profile.d/cargo.sh      # system-wide rc files
  # When this list is set, the default ~/.bashrc auto-source is NOT added —
  # include it explicitly if you want both:
  #   - ~/.bashrc
  #   - ~/.zshrc

Missing files are skipped silently. Sourcing happens in bash, so files that rely on zsh-only syntax may error — if that's a concern, source just the PATH-setting portion (e.g. nvm's nvm.sh directly) rather than the whole rc file.

To disable the auto-source behaviour (strict login-shell semantics only):

terminal:
  auto_source_bashrc: false

uv: command not found

Cause: The uv package manager isn't installed or not in PATH.

Solution:

curl -LsSf https://astral.sh/uv/install.sh | sh
source ~/.bashrc

Permission denied errors during install

Cause: Insufficient permissions to write to the install directory.

Solution:

sudo rm /usr/local/bin/hermes
curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash

---

Provider & Model Issues

/model only shows one provider / can't switch providers

Cause: /model (inside a chat session) can only switch between providers you've already configured. If you've only set up OpenRouter, that's all /model will show.

Solution: Exit your session and use hermes model from your terminal to add new providers: