https://github.com/deepseek-ai/awesome-deepseek-agent/blob/main/docs/hermes.md

这是 DeepSeek 开源整合的地址。

Hermes is a self-improving AI agent built by Nous Research. It includes a built-in learning loop: it creates skills from experience, improves them during use, persists knowledge, and builds an evolving model of your preferences across sessions.

Hermes 是由 Nous Research 开发的一款具备自我提升能力的 AI 智能体。它内置了学习循环机制：能够从经验中习得技能并在使用过程中加以改进，持久保存知识，并跨会话构建关于你偏好的演进式模型。

1. Install Hermes

Quick Install

Get Hermes Agent up and running in under two minutes with the one-line installer.

Linux / macOS / WSL2

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

The only prerequisite is Git. The installer automatically handles everything else.

For more installation instructions, please refer to the Hermes installation page.

2. Run and Configure

Reload your shell and start Hermes configuration:

• Execute the hermes setup command
• Choose the Quick Setup option
• When prompted for the model provider, select DeepSeek
• Enter your DeepSeek API Key
• Enter the Base URL as https://api.deepseek.com
• Select the deepseek-v4-pro model
• Continue with the remaining options

What the Installer Does

The installer handles everything automatically — all dependencies (Python, Node.js, ripgrep, ffmpeg), the repo clone, virtual environment, global hermes command setup, and LLM provider configuration. By the end, you're ready to chat.

Install Layout

Where the installer puts things depends on whether you're installing as a normal user or as root:

Installer	Code lives at	hermes binary	Data directory
Per-user (git installer)	~/.hermes/hermes-agent/	~/.local/bin/hermes (symlink)	~/.hermes/
Root-mode (sudo curl … | sudo bash)	/usr/local/lib/hermes-agent/	/usr/local/bin/hermes	/root/.hermes/ (or $HERMES_HOME)

The root-mode FHS layout (/usr/local/lib/…, /usr/local/bin/hermes) matches where other system-wide developer tools land on Linux. It's useful for shared-machine deployments where one system install should serve every user. Per-user config (auth, skills, sessions) still lives under each user's ~/.hermes/ or explicit HERMES_HOME.

After Installation

Reload your shell and start chatting:

source ~/.bashrc   # or: source ~/.zshrc
hermes             # Start chatting!

To reconfigure individual settings later, use the dedicated commands:

hermes model          # Choose your LLM provider and model
hermes tools          # Configure which tools are enabled
hermes gateway setup  # Set up messaging platforms
hermes config set     # Set individual config values
hermes setup          # Or run the full setup wizard to configure everything at once

Fastest path: Nous Portal

One subscription covers 300+ models plus the Tool Gateway (web search, image generation, TTS, cloud browser). Skip the per-tool key juggling:

hermes setup --portal

That logs you in, sets Nous as your provider, and turns on the Tool Gateway in one command.

---

Prerequisites

Installer: On non-Windows platforms, the only prerequisite is Git. On Linux, also make sure curl and xz-utils are available (the installer downloads Node.js as a .tar.xz archive). The desktop app additionally requires g++ (or build-essential on Debian/Ubuntu) to compile native modules. The installer automatically handles everything else:

• uv (fast Python package manager)
• Python 3.11 (via uv, no sudo needed)
• Node.js v22 (for browser automation and WhatsApp bridge)
• ripgrep (fast file search)
• ffmpeg (audio format conversion for TTS)

info

You do not need to install Python, Node.js, ripgrep, or ffmpeg manually. The installer detects what's missing and installs it for you. Just make sure git is available (git --version). On Linux, ensure curl and xz-utils are installed (sudo apt install curl xz-utils on Debian/Ubuntu). For the desktop app, also install build-essential (sudo apt install build-essential).

Nix users

Nix is no longer an explicitly supported install path (best-effort only). If you already use Nix (on NixOS, macOS, or Linux), there's a dedicated setup path with a Nix flake, declarative NixOS module, and optional container mode. See the Nix & NixOS Setup guide.

---

Manual / Developer Installation

If you want to clone the repo and install from source — for contributing, running from a specific branch, or having full control over the virtual environment — see the Development Setup section in the Contributing guide.

---

Non-Sudo / System Service User Installs

Running Hermes as a dedicated unprivileged user (e.g. a hermes systemd service account, or any user without sudo access) is supported. The only thing on the install path that genuinely needs root is Playwright's --with-deps step, which apt-installs shared libraries (libnss3, libxkbcommon, etc.) used by Chromium. The installer detects whether sudo is available and gracefully degrades when it isn't — it will install the Chromium binary into the service user's own Playwright cache and print the exact command an administrator needs to run separately.

支持以专用的非特权用户（例如 `hermes` systemd 服务账户，或任何没有 `sudo` 权限的用户）身份运行 Hermes。在安装过程中，唯一真正需要 root 权限的步骤是 Playwright 的 `--with-deps` 环节，该步骤会通过 `apt` 安装 Chromium 所需的共享库（如 `libnss3`、`libxkbcommon` 等）。安装程序会自动检测是否存在 `sudo` 权限；若无权限，则会采取降级处理：将 Chromium 二进制文件安装到服务用户自己的 Playwright 缓存目录中，并输出管理员需单独执行的具体命令。

Recommended split (Debian/Ubuntu):

1. One time, as an admin user with sudo, install the system libraries Chromium needs:

   sudo npx playwright install-deps chromium
   

   (You can run this from anywhere — npx will fetch Playwright on the fly.)

2. As the unprivileged service user, run the regular installer. It will detect the missing sudo, skip --with-deps, and install Chromium into the user's local Playwright cache:

   curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash
   

   If you want to skip the Playwright step entirely — for example because you're running headless and don't need browser automation — pass --skip-browser:

   curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash -s -- --skip-browser
   

3. Make hermes available to the service user's shells. The installer writes the launcher to ~/.local/bin/hermes. System service accounts often have a minimal PATH that doesn't include ~/.local/bin. Either add it to the user's environment, or symlink the launcher into a system location:

   # Option A — add to the service user's profile
   echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc
   
   # Option B — symlink system-wide (run as an admin)
   sudo ln -s /home/hermes/.hermes/hermes-agent/venv/bin/hermes /usr/local/bin/hermes
   

4. Verify: hermes doctor should now run cleanly. If you get ModuleNotFoundError: No module named 'dotenv', you're invoking the repo source hermes file (~/.hermes/hermes-agent/hermes) with system Python instead of the venv launcher (~/.hermes/hermes-agent/venv/bin/hermes) — fix step 3.

The same pattern works on Arch (the installer uses pacman with the same sudo-detection logic), Fedora/RHEL, and openSUSE — those distros don't support --with-deps at all, so an administrator always installs the system libraries separately. The relevant dnf/zypper commands are printed by the installer.

---

Troubleshooting

Problem	Solution
hermes: command not found	Reload your shell (source ~/.bashrc) or check PATH
API key not set	Run hermes model to configure your provider, or hermes config set OPENROUTER_API_KEY your_key
Missing config after update	Run hermes config check then hermes config migrate

For more diagnostics, run hermes doctor — it will tell you exactly what's missing and how to fix it.

Install method auto-detection

Hermes auto-detects whether it was installed via pip, the git installer, Homebrew, or NixOS, and hermes update prints the matching update command for that path. There's no env var to set — the detection is based on the install layout (Python site-packages, ~/.hermes/hermes-agent/, Homebrew prefix, or Nix store path). hermes doctor also surfaces the detected method under its environment summary.