All apps · 0 apps
hermes-agent
Docker app from rorar's Repository
Overview
Readme
View on GitHub
Hermes Agent ☤
The self-improving AI agent built by Nous Research. It's the only agent with a built-in learning loop — it creates skills from experience, improves them during use, nudges itself to persist knowledge, searches its own past conversations, and builds a deepening model of who you are across sessions. Run it on a $5 VPS, a GPU cluster, or serverless infrastructure that costs nearly nothing when idle. It's not tied to your laptop — talk to it from Telegram while it works on a cloud VM.
Use any model you want — Nous Portal, OpenRouter, OpenAI, your own endpoint, and many others. Switch with hermes model — no code changes, no lock-in.
| A real terminal interface | Full TUI with multiline editing, slash-command autocomplete, conversation history, interrupt-and-redirect, and streaming tool output. |
| Lives where you do | Telegram, Discord, Slack, WhatsApp, Signal, and CLI — all from a single gateway process. Voice memo transcription, cross-platform conversation continuity. |
| A closed learning loop | Agent-curated memory with periodic nudges. Autonomous skill creation after complex tasks. Skills self-improve during use. FTS5 session search with LLM summarization for cross-session recall. Honcho dialectic user modeling. Compatible with the agentskills.io open standard. |
| Scheduled automations | Built-in cron scheduler with delivery to any platform. Daily reports, nightly backups, weekly audits — all in natural language, running unattended. |
| Delegates and parallelizes | Spawn isolated subagents for parallel workstreams. Write Python scripts that call tools via RPC, collapsing multi-step pipelines into zero-context-cost turns. |
| Runs anywhere, not just your laptop | Six terminal backends — local, Docker, SSH, Singularity, Modal, and Daytona. Daytona and Modal offer serverless persistence — your agent's environment hibernates when idle and wakes on demand, costing nearly nothing between sessions. Run it on a $5 VPS or a GPU cluster. |
| Research-ready | Batch trajectory generation, trajectory compression for training the next generation of tool-calling models. |
Quick Install
Linux, macOS, WSL2, Termux
curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash
Windows (native, PowerShell)
Heads up: Native Windows runs Hermes without WSL — CLI, gateway, TUI, and tools all work natively. If you'd rather use WSL2, the Linux/macOS one-liner above works there too. Found a bug? Please file issues.
Run this in PowerShell:
iex (irm https://hermes-agent.nousresearch.com/install.ps1)
The installer handles everything: uv, Python 3.11, Node.js, ripgrep, ffmpeg, and a portable Git Bash (MinGit, unpacked to %LOCALAPPDATA%\hermes\git — no admin required, completely isolated from any system Git install). Hermes uses this bundled Git Bash to run shell commands.
If you already have Git installed, the installer detects it and uses that instead. Otherwise a ~45MB MinGit download is all you need — it won't touch or interfere with any system Git.
Android / Termux: The tested manual path is documented in the Termux guide. On Termux, Hermes installs a curated
.[termux]extra because the full.[all]extra currently pulls Android-incompatible voice dependencies.Windows: Native Windows is fully supported — the PowerShell one-liner above installs everything. If you'd rather use WSL2, the Linux command works there too. Native Windows install lives under
%LOCALAPPDATA%\hermes; WSL2 installs under~/.hermesas on Linux.
After installation:
source ~/.bashrc # reload shell (or: source ~/.zshrc)
hermes # start chatting!
Troubleshooting
Windows Defender or antivirus flags uv.exe as malware
If your antivirus (Bitdefender, Windows Defender, etc.) quarantines uv.exe from the Hermes bin folder (%LOCALAPPDATA%\hermes\bin\uv.exe), this is a false positive. The file is Astral's uv — the Rust Python package manager Hermes bundles to manage its Python environment. ML-based antivirus engines commonly flag unsigned Rust binaries that download and install packages.
To verify your copy is authentic:
# Install GitHub CLI if needed
winget install --id GitHub.cli
# Login to GitHub
gh auth login
# Run verification
$uv = "$env:LOCALAPPDATA\hermes\bin\uv.exe"
$ver = (& $uv --version).Split(' ')[1]
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
$zip = "$env:TEMP\uv.zip"
Invoke-WebRequest "https://github.com/astral-sh/uv/releases/download/$ver/uv-x86_64-pc-windows-msvc.zip" -OutFile $zip -UseBasicParsing
gh attestation verify $zip --repo astral-sh/uv
Expand-Archive $zip "$env:TEMP\uv_x" -Force
(Get-FileHash "$env:TEMP\uv_x\uv.exe").Hash -eq (Get-FileHash $uv).Hash
If attestation says "Verification succeeded" and the last line prints True, you're good.
To whitelist Hermes:
- Windows Defender: Run PowerShell as Admin →
Add-MpPreference -ExclusionPath "$env:LOCALAPPDATA\hermes\bin" - Bitdefender: Add an exception in the Bitdefender console (Protection > Antivirus > Settings > Manage Exceptions)
- Whitelist the folder, not the file hash — Hermes updates
uvand the hash changes every version
For more context, see the upstream Astral reports: astral-sh/uv#13553, astral-sh/uv#15011, astral-sh/uv#10079.
Getting Started
hermes # Interactive CLI — start a conversation
hermes model # Choose your LLM provider and model
hermes tools # Configure which tools are enabled
hermes config set # Set individual config values
hermes config get # Print individual config values
hermes gateway # Start the messaging gateway (Telegram, Discord, etc.)
hermes setup # Run the full setup wizard (configures everything at once)
hermes claw migrate # Migrate from OpenClaw (if coming from OpenClaw)
hermes update # Update to the latest version
hermes doctor # Diagnose any issues
Skip the API-key collection — Nous Portal
Hermes works with whatever provider you want — that's not changing. But if you'd rather not collect five separate API keys for the model, web search, image generation, TTS, and a cloud browser, Nous Portal covers all of them under one subscription:
- 300+ models — pick any of them with
/model <name> - Tool Gateway — web search (Firecrawl), image generation (FAL), text-to-speech (OpenAI), cloud browser (Browser Use), all routed through your sub. No extra accounts.
One command from a fresh install:
hermes setup --portal
That logs you in via OAuth, sets Nous as your provider, and turns on the Tool Gateway. Check what's wired up any time with hermes portal info. Full details on the Tool Gateway docs page.
You can still bring your own keys per-tool whenever you want — the gateway is per-backend, not all-or-nothing.
CLI vs Messaging Quick Reference
Hermes has two entry points: start the terminal UI with hermes, or run the gateway and talk to it from Telegram, Discord, Slack, WhatsApp, Signal, or Email. Once you're in a conversation, many slash commands are shared across both interfaces.
| Action | CLI | Messaging platforms |
|---|---|---|
| Start chatting | hermes |
Run hermes gateway setup + hermes gateway start, then send the bot a message |
| Start fresh conversation | /new or /reset |
/new or /reset |
| Change model | /model [provider:model] |
/model [provider:model] |
| Set a personality | /personality [name] |
/personality [name] |
| Retry or undo the last turn | /retry, /undo |
/retry, /undo |
| Compress context / check usage | /compress, /usage, /insights [--days N] |
/compress, /usage, /insights [days] |
| Browse skills | /skills or /<skill-name> |
/<skill-name> |
| Interrupt current work | Ctrl+C or send a new message |
/stop or send a new message |
| Platform-specific status | /platforms |
/status, /sethome |
For the full command lists, see the CLI guide and the Messaging Gateway guide.
Documentation
All documentation lives at hermes-agent.nousresearch.com/docs:
| Section | What's Covered |
|---|---|
| Quickstart | Install → setup → first conversation in 2 minutes |
| CLI Usage | Commands, keybindings, personalities, sessions |
| Configuration | Config file, providers, models, all options |
| Messaging Gateway | Telegram, Discord, Slack, WhatsApp, Signal, Home Assistant |
| Security | Command approval, DM pairing, container isolation |
| Tools & Toolsets | 40+ tools, toolset system, terminal backends |
| Skills System | Procedural memory, Skills Hub, creating skills |
| Memory | Persistent memory, user profiles, best practices |
| MCP Integration | Connect any MCP server for extended capabilities |
| Cron Scheduling | Scheduled tasks with platform delivery |
| Context Files | Project context that shapes every conversation |
| Architecture | Project structure, agent loop, key classes |
| Contributing | Development setup, PR process, code style |
| CLI Reference | All commands and flags |
| Environment Variables | Complete env var reference |
Migrating from OpenClaw
If you're coming from OpenClaw, Hermes can automatically import your settings, memories, skills, and API keys.
During first-time setup: The setup wizard (hermes setup) automatically detects ~/.openclaw and offers to migrate before configuration begins.
Anytime after install:
hermes claw migrate # Interactive migration (full preset)
hermes claw migrate --dry-run # Preview what would be migrated
hermes claw migrate --preset user-data # Migrate without secrets
hermes claw migrate --overwrite # Overwrite existing conflicts
What gets imported:
- SOUL.md — persona file
- Memories — MEMORY.md and USER.md entries
- Skills — user-created skills →
~/.hermes/skills/openclaw-imports/ - Command allowlist — approval patterns
- Messaging settings — platform configs, allowed users, working directory
- API keys — allowlisted secrets (Telegram, OpenRouter, OpenAI, Anthropic, ElevenLabs)
- TTS assets — workspace audio files
- Workspace instructions — AGENTS.md (with
--workspace-target)
See hermes claw migrate --help for all options, or use the openclaw-migration skill for an interactive agent-guided migration with dry-run previews.
Contributing
We welcome contributions! See the Contributing Guide for development setup, code style, and PR process.
Quick start for contributors — use the standard installer, then work from the
full git checkout it creates at $HERMES_HOME/hermes-agent (usually
~/.hermes/hermes-agent). This matches the layout used by hermes update, the
managed venv, lazy dependencies, gateway, and docs tooling.
curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash
cd "${HERMES_HOME:-$HOME/.hermes}/hermes-agent"
uv pip install -e ".[all,dev]"
scripts/run_tests.sh
Manual clone fallback (for throwaway clones/CI where you intentionally do not want the managed install layout):
Create the venv outside the cloned source tree — a venv inside the directory the agent operates from can be wiped by a relative-path command the agent runs against its own checkout, destroying the running runtime mid-session.
curl -LsSf https://astral.sh/uv/install.sh | sh
uv venv ~/.hermes/venvs/hermes-dev --python 3.11
source ~/.hermes/venvs/hermes-dev/bin/activate
uv pip install -e ".[all,dev]"
scripts/run_tests.sh
Community
- 💬 Discord
- 📚 Skills Hub
- 🐛 Issues
- 🔌 computer-use-linux — Linux desktop-control MCP server for Hermes and other MCP hosts, with AT-SPI accessibility trees, Wayland/X11 input, screenshots, and compositor window targeting.
- 🔌 HermesClaw — Community WeChat bridge: Run Hermes Agent and OpenClaw on the same WeChat account.
License
MIT — see LICENSE.
Built by Nous Research.
Install hermes-agent on Unraid in a few clicks.
Find hermes-agent in Community Apps on your Unraid server, review the template, and click Install. Unraid handles the Docker app or plugin setup from the published template.
Requirements
Download Statistics
Related apps
Explore more like this
Explore allLinks
Details
nousresearch/hermes-agent:latestRuntime arguments
- Web UI
http://[IP]:[PORT:9119]- Network
bridge- Shell
bash- Extra Params
--shm-size=1g --user 0:0 --hostname=hermes-agent --restart=unless-stopped
Template configuration
HTTP port for the web dashboard. After setup, configure Hermes to run the dashboard command. See: https://hermes-agent.nousresearch.com/docs/user-guide/features/web-dashboard
- Target
- 9119
- Default
- 9119
Persistent config directory for Hermes (.env, config.yaml, skills, memories, logs).
- Target
- /opt/data
- Default
- /mnt/user/appdata/hermes-agent
Timezone for scheduling. See: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List
- Target
- TZ
- Default
- Europe/Berlin
Docs: https://hermes-agent.nousresearch.com/docs
Enable the built-in HTTP API server (required for dashboard and integrations).
- Target
- API_SERVER_ENABLED
- Default
- true
Host address for the API server (0.0.0.0 for all interfaces).
- Target
- API_SERVER_HOST
- Default
- 0.0.0.0
Port for the API server.
- Target
- API_SERVER_PORT
- Default
- 8642
Bearer token for API authentication. Required when binding to non-localhost. Use the same value in Open WebUI. Generate with: openssl rand -hex 32
- Target
- API_SERVER_KEY
Docs: https://hermes-agent.nousresearch.com/docs/user-guide/messaging/matrix
Matrix homeserver URL.
- Target
- MATRIX_HOMESERVER
- Default
- https://matrix-client.matrix.org
Matrix access token (recommended). User ID is auto-detected from token.
- Target
- MATRIX_ACCESS_TOKEN
Matrix user ID. Not required if MATRIX_ACCESS_TOKEN is set.
- Target
- MATRIX_USER_ID
Matrix password. Not required if MATRIX_ACCESS_TOKEN is set.
- Target
- MATRIX_PASSWORD
Matrix recovery key for cross-signing (for E2EE).
- Target
- MATRIX_RECOVERY_KEY
Matrix device ID (leave empty for auto-generated).
- Target
- MATRIX_DEVICE_ID
- Default
- HERMES_BOT
Matrix room ID for bot's home room (for cron notifications).
- Target
- MATRIX_HOME_ROOM
Comma-separated list of allowed Matrix user IDs (empty = deny all except self).
- Target
- MATRIX_ALLOWED_USERS
Enable end-to-end encryption (requires libolm).
- Target
- MATRIX_ENCRYPTION
- Default
- true
Bot only responds when mentioned in rooms (DMs always respond).
- Target
- MATRIX_REQUIRE_MENTION
- Default
- false
Show emoji reactions during message processing.
- Target
- MATRIX_REACTIONS
- Default
- true
Auto-create threads for responses in rooms.
- Target
- MATRIX_AUTO_THREAD
- Default
- true
Comma-separated room IDs that respond without mention.
- Target
- MATRIX_FREE_RESPONSE_ROOMS
Docs: https://hermes-agent.nousresearch.com/docs/user-guide/messaging/telegram
Telegram bot token from @BotFather.
- Target
- TELEGRAM_BOT_TOKEN
Comma-separated list of allowed Telegram user IDs.
- Target
- TELEGRAM_ALLOWED_USERS
Docs: https://hermes-agent.nousresearch.com/docs/user-guide/messaging/discord
Discord bot token.
- Target
- DISCORD_BOT_TOKEN
Discord guild/server ID.
- Target
- DISCORD_GUILD_ID
Docs: https://hermes-agent.nousresearch.com/docs/user-guide/messaging/slack
Slack Bot Token (xoxb-...).
- Target
- SLACK_BOT_TOKEN
Slack App Token (xapp-...).
- Target
- SLACK_APP_TOKEN
Docs: https://hermes-agent.nousresearch.com/docs
OpenAI API key.
- Target
- OPENAI_API_KEY
OpenRouter API key.
- Target
- OPENROUTER_API_KEY
Anthropic API key (for Claude).
- Target
- ANTHROPIC_API_KEY
Google AI API key (for Gemini).
- Target
- GOOGLE_API_KEY
DeepSeek API key.
- Target
- DEEPSEEK_API_KEY
Groq API key (for Groq Whisper STT).
- Target
- GROQ_API_KEY
Ollama base URL (e.g. http://host:11434).
- Target
- OLLAMA_BASE_URL
Custom OpenAI-compatible API base URL.
- Target
- OPENAI_BASE_URL
z.ai / ZhipuAI GLM API key.
- Target
- GLM_API_KEY
Kimi / Moonshot API key.
- Target
- KIMI_API_KEY
MiniMax global API key.
- Target
- MINIMAX_API_KEY
MiniMax China endpoint API key.
- Target
- MINIMAX_CN_API_KEY
Kilo Code API key.
- Target
- KILOCODE_API_KEY
Xiaomi MiMo API key.
- Target
- XIAOMI_API_KEY
Hugging Face Inference Providers token.
- Target
- HF_TOKEN
Alibaba DashScope API key.
- Target
- DASHSCOPE_API_KEY
OpenCode Zen API key.
- Target
- OPENCODE_ZEN_API_KEY
OpenCode Go API key.
- Target
- OPENCODE_GO_API_KEY
Vercel AI Gateway API key.
- Target
- AI_GATEWAY_API_KEY
Tavily API key for AI-native web search, extract, and crawl.
- Target
- TAVILY_API_KEY
Exa API key for AI-native web search and content retrieval.
- Target
- EXA_API_KEY
Docs: https://hermes-agent.nousresearch.com/docs
Sudo password for the container (stored in plaintext - use with caution).
- Target
- SUDO_PASSWORD
UID for the hermes user inside container. Match to your Unraid user (default: nobody). Set to 0 for root.
- Target
- HERMES_UID
- Default
- 99
GID for the hermes user. Match to your Unraid users group.
- Target
- HERMES_GID
- Default
- 100
UMASK for files created by the container.
- Target
- UMASK
- Default
- 000
Home directory for Hermes config and data.
- Target
- HERMES_HOME
- Default
- /opt/data