
hermes-agent
記憶とスキルを自分で書き足していく常駐エージェント。端末のTUIからもTelegramからも同じ会話を続けられます。
概要
Nous Research自身が開発するエージェント本体で、TUIと単一のgatewayプロセスがTelegram、Discord、Slack、WhatsApp、Signal、Emailの会話を束ね、cronスケジューラ、隔離されたサブエージェント、local/Docker/SSH/Singularity/Modal/Daytona/Vercel Sandboxという7種類のターミナルバックエンドを備えます。核になるのは閉じた学習ループで、定期的な促しに応じて記憶を整理し、複雑なタスクの後に自らスキルを作り、FTS5とLLM要約で過去セッションを検索します。裏を返せば、有用さの源である状態が`~/.hermes`配下に溜まり続け、バージョン管理の外で育つため、定期的な棚卸しが前提になります。組み込み用のライブラリではなく運用するアシスタントであり、READMEが記載するのはhermesのサブコマンドとスラッシュコマンドで、埋め込み用のAPIではありません。自作コードから呼ぶエージェントループが欲しい用途には向きません。シェルを扱えるエージェントをチャット経由で露出させる以上、コマンド承認とDMペアリングの設定は任意の飾りではなくなります。
hermes-agentで何ができますか?
- サーバーに置いてスマホから話しかける —
hermes gateway setupとhermes gateway startでgatewayを起動すると、Telegram、Discord、Slack、WhatsApp、Signal、Emailを1つのプロセスが受け持ちます。ボイスメモは文字起こしされ、会話はプラットフォームをまたいで継続します。/modelや/compress、/undoは両方の入口で使えますが、すべてが同一というわけではありません。使用状況の確認はCLIが/insights [--days N]、チャット側は/insights [days]、割り込みはTUIがCtrl+Cでチャットは/stopになります。 - 使わない間は環境を眠らせる — ターミナルバックエンドはlocal、Docker、SSH、Singularity、Modal、Daytona、Vercel Sandboxの7種類です。DaytonaとModalはサーバーレス永続化に対応し、アイドル時に環境がハイバネートして必要になった時点で復帰するため、放置中のコストがほぼかかりません。
- モデルもツール提供元もコードを触らず差し替える —
hermes modelではプロバイダとモデル(OpenRouter、OpenAI、Nous Portal、自前エンドポイント)を選びます。hermes setup --portalはOAuthログインとTool Gatewayの有効化までを一度に行い、Web検索(Firecrawl)、画像生成(FAL)、TTS(OpenAI)、クラウドブラウザ(Browser Use)を1つのサブスクリプションに寄せます。gatewayはバックエンド単位なので、ツールごとに自前のキーを使う運用も残せます。配線状況はhermes portal infoで確認します。 - OpenClawの資産を引き継ぐ —
hermes claw migrateがSOUL.md、MEMORY.mdとUSER.mdの記憶、ユーザー作成スキル(~/.hermes/skills/openclaw-imports/へ)、コマンド許可リスト、メッセージング設定、許可済みAPIキーを取り込みます。--dry-runで対象を先に確認でき、--preset user-dataならシークレットを除いて移行します。初回のhermes setupは~/.openclawを自動検出します。 - 無人実行と並列処理を任せる — 組み込みのcronスケジューラは自然言語で書いたタスクを無人実行し、結果を連携済みのプラットフォームへ配信します。設定は
docs/user-guide/features/cronに記載があります。並列の作業は隔離されたサブエージェントへ切り出し、RPC経由でツールを呼ぶPythonスクリプトを書けば、多段のパイプラインをコンテキスト消費のない1ターンに畳めます。ただしREADMEのコマンド一覧にスケジュール用のサブコマンドはなく、入口は会話の中になります。
ドキュメント
NousResearch/hermes-agent のREADMEより転載(MIT)。 原文を読む ↗
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.
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]:https://github.com/NousResearch/hermes-agent/blob/main/: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.
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.