- Python 71.3%
- TypeScript 24.9%
- JavaScript 1.9%
- Shell 0.4%
- PowerShell 0.4%
- Other 0.9%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
|
Some checks are pending
CI / Detect affected areas (push) Waiting to run
CI / Python tests (push) Blocked by required conditions
CI / OS-specific tests (push) Blocked by required conditions
CI / Python lints (push) Blocked by required conditions
CI / JS & TS checks (push) Blocked by required conditions
CI / Rust tests (push) Blocked by required conditions
CI / Catalog tests (push) Blocked by required conditions
CI / Remote terminal backends (push) Blocked by required conditions
CI / Bootstrap installer (push) Blocked by required conditions
CI / Desktop E2E (push) Blocked by required conditions
CI / Desktop core E2E (push) Blocked by required conditions
CI / Desktop update E2E (push) Blocked by required conditions
CI / Docs Site (push) Blocked by required conditions
CI / Deny unrelated histories (push) Blocked by required conditions
CI / Check contributors (push) Blocked by required conditions
CI / Check uv.lock (push) Blocked by required conditions
CI / Check no committed infographics (push) Blocked by required conditions
CI / Profile artifact check (push) Blocked by required conditions
CI / Prompt surface diff (push) Blocked by required conditions
CI / Icon assets freshness (push) Blocked by required conditions
CI / Check no case-colliding filenames (push) Blocked by required conditions
CI / Check no large binaries (push) Blocked by required conditions
CI / No production imports of the tools.lazy_deps stub (push) Blocked by required conditions
CI / package-lock.json diff (push) Blocked by required conditions
CI / Lint Docker scripts (push) Blocked by required conditions
CI / Supply-chain scan (push) Blocked by required conditions
CI / All required checks pass (v2) (push) Blocked by required conditions
CI / CI timing report (push) Blocked by required conditions
CI / JS & TS checks-1 (push) Blocked by required conditions
CI / cargo test (bootstrap installer) (push) Blocked by required conditions
CI / Catalog tests-1 (push) Blocked by required conditions
CI / SSH + Docker backends (real sshd, real daemon) (push) Blocked by required conditions
CI / install.sh protocol + small fresh-install E2E (push) Blocked by required conditions
CI / install.ps1 protocol surface (push) Blocked by required conditions
CI / Playwright E2E (Linux) (push) Blocked by required conditions
CI / Desktop core E2E (Linux) (push) Blocked by required conditions
CI / Desktop install/update E2E (Linux, app-update) (push) Blocked by required conditions
CI / Desktop install/update E2E (Linux, build-fail) (push) Blocked by required conditions
CI / Desktop install/update E2E (Linux, first-run) (push) Blocked by required conditions
CI / Desktop install/update E2E (Linux, update-concurrency) (push) Blocked by required conditions
CI / docs-site-checks (push) Blocked by required conditions
CI / check-common-ancestor (push) Blocked by required conditions
CI / check-attribution (push) Blocked by required conditions
CI / python -m pm.build_env --source . --check-lock (push) Blocked by required conditions
CI / check-no-committed-infographics (push) Blocked by required conditions
CI / Reject profile archives (push) Blocked by required conditions
CI / Regenerate icons + diff against committed (push) Blocked by required conditions
CI / check-case-collisions (push) Blocked by required conditions
CI / Reject large binaries (push) Blocked by required conditions
CI / No production imports of the tools.lazy_deps stub-1 (push) Blocked by required conditions
CI / package-lock.json semantic diff (push) Blocked by required conditions
CI / Prompt surface summary (push) Blocked by required conditions
CI / Lint Dockerfile (hadolint) (push) Blocked by required conditions
Docker Build, Test, and Publish / Resolve release phase (push) Waiting to run
Docker Build, Test, and Publish / Detect affected areas (push) Blocked by required conditions
Docker Build, Test, and Publish / Build and test image (desktop/amd64) (push) Blocked by required conditions
Docker Build, Test, and Publish / Build and test image (slim/amd64) (push) Blocked by required conditions
Docker Build, Test, and Publish / Build and test image (desktop/arm64) (push) Blocked by required conditions
Docker Build, Test, and Publish / Build and test image (slim/arm64) (push) Blocked by required conditions
Docker Build, Test, and Publish / publish (amd64, linux/amd64, blacksmith-32vcpu-ubuntu-2404, desktop) (push) Blocked by required conditions
Docker Build, Test, and Publish / publish (amd64, linux/amd64, blacksmith-32vcpu-ubuntu-2404, slim) (push) Blocked by required conditions
Docker Build, Test, and Publish / publish (arm64, linux/arm64, blacksmith-32vcpu-ubuntu-2404-arm, desktop) (push) Blocked by required conditions
Docker Build, Test, and Publish / publish (arm64, linux/arm64, blacksmith-32vcpu-ubuntu-2404-arm, slim) (push) Blocked by required conditions
Docker Build, Test, and Publish / merge (, slim) (push) Blocked by required conditions
Docker Build, Test, and Publish / merge (-desktop, desktop) (push) Blocked by required conditions
Docker Build, Test, and Publish / Publish tested Docker image (desktop/amd64) (push) Blocked by required conditions
Docker Build, Test, and Publish / Publish tested Docker image (slim/amd64) (push) Blocked by required conditions
Docker Build, Test, and Publish / Publish tested Docker image (desktop/arm64) (push) Blocked by required conditions
Docker Build, Test, and Publish / Publish tested Docker image (slim/arm64) (push) Blocked by required conditions
Docker Build, Test, and Publish / Assemble versioned manifest and digest receipt (push) Blocked by required conditions
Docker Build, Test, and Publish / Docker phase requirements met (push) Blocked by required conditions
Nix flake check / Detect affected areas (push) Waiting to run
Nix flake check / nix flake check (push) Blocked by required conditions
The key left DEFAULT_CONFIG with the backend, but the singularity plugin reads it and its setup text says `hermes config set terminal.singularity_image <image>`; set and get now flagged it "not a recognized config key ... Hermes may not read it". A seeded default would hide the plugin's TERMINAL_SINGULARITY_IMAGE fallback, so _validate_config_key accepts left_core_migration.LEFT_CORE_TERMINAL_KEYS (the renamed RETIRED_TERMINAL_ENV_COPIES, which unset already consults) instead. The wrong-prefix refusal text moves to hermes_cli/config_key_notices.py to keep config.py under its line cap. Review: https://github.com/NousResearch/hermes-agent/pull/142561#pullrequestreview (kshitijk4poor, item 2) |
||
| .github | ||
| acp_adapter | ||
| agent | ||
| apps | ||
| assets | ||
| contributors | ||
| cron | ||
| docker | ||
| evals | ||
| gateway | ||
| hermes_cli | ||
| hermes_platform | ||
| locales | ||
| native/fts5_cjk | ||
| nix | ||
| optional-mcps | ||
| optional-skills | ||
| plugin-catalog | ||
| plugins | ||
| pm | ||
| providers | ||
| scripts | ||
| skills | ||
| tests | ||
| tests-js | ||
| tools | ||
| tui_gateway | ||
| ui-tui | ||
| web | ||
| website | ||
| .coderabbit.yaml | ||
| .dockerignore | ||
| .env.example | ||
| .envrc | ||
| .gitattributes | ||
| .gitignore | ||
| .hadolint.yaml | ||
| .mailmap | ||
| .npmrc | ||
| .nvmrc | ||
| .prettierignore | ||
| .prettierrc | ||
| .python-version | ||
| activate | ||
| activate.fish | ||
| activate.ps1 | ||
| AGENTS.md | ||
| batch_runner.py | ||
| cli-config.yaml.example | ||
| cli.py | ||
| CONTRIBUTING.es.md | ||
| CONTRIBUTING.md | ||
| docker-compose.windows.yml | ||
| docker-compose.yml | ||
| Dockerfile | ||
| eslint.config.shared.mjs | ||
| flake.lock | ||
| flake.nix | ||
| hermes | ||
| hermes_bootstrap.py | ||
| hermes_constants.py | ||
| hermes_constants_scratch.py | ||
| hermes_constants_scratch_stuck.py | ||
| hermes_dir_acl.py | ||
| hermes_logging.py | ||
| hermes_startup_watchdog.py | ||
| hermes_state.py | ||
| hermes_state_api_content.py | ||
| hermes_state_common.py | ||
| hermes_state_compression.py | ||
| hermes_state_coverage.py | ||
| hermes_state_dbfile.py | ||
| hermes_state_detached_results.py | ||
| hermes_state_errors.py | ||
| hermes_state_fts.py | ||
| hermes_state_gateway.py | ||
| hermes_state_guard.py | ||
| hermes_state_health.py | ||
| hermes_state_holders.py | ||
| hermes_state_identity.py | ||
| hermes_state_ids.py | ||
| hermes_state_keys.py | ||
| hermes_state_local.py | ||
| hermes_state_local_lineage.py | ||
| hermes_state_local_migration.py | ||
| hermes_state_lockguard.py | ||
| hermes_state_lockowners.py | ||
| hermes_state_maintenance.py | ||
| hermes_state_media.py | ||
| hermes_state_messages.py | ||
| hermes_state_mutation_binding.py | ||
| hermes_state_mutation_branch.py | ||
| hermes_state_mutation_chat_pick.py | ||
| hermes_state_mutation_compress.py | ||
| hermes_state_mutation_guards.py | ||
| hermes_state_mutation_prepared.py | ||
| hermes_state_mutation_reset.py | ||
| hermes_state_mutation_retirement.py | ||
| hermes_state_mutation_transcript.py | ||
| hermes_state_mutations.py | ||
| hermes_state_pidns.py | ||
| hermes_state_portability.py | ||
| hermes_state_profile_repair.py | ||
| hermes_state_prune_rewrite.py | ||
| hermes_state_readpool.py | ||
| hermes_state_reconcile.py | ||
| hermes_state_registry.py | ||
| hermes_state_repair.py | ||
| hermes_state_rewind.py | ||
| hermes_state_runtime.py | ||
| hermes_state_runtime_workers.py | ||
| hermes_state_schema.py | ||
| hermes_state_search.py | ||
| hermes_state_sessions.py | ||
| hermes_state_sessions_model_config.py | ||
| hermes_state_telegram.py | ||
| hermes_state_terminal.py | ||
| hermes_state_timeline.py | ||
| hermes_state_titles.py | ||
| hermes_state_todo.py | ||
| hermes_state_usage.py | ||
| hermes_state_user_copy.py | ||
| hermes_state_wal.py | ||
| hermes_state_worker_compression.py | ||
| hermes_state_worker_context.py | ||
| hermes_state_worker_lifecycle.py | ||
| hermes_time.py | ||
| hermes_yaml.py | ||
| justfile | ||
| lefthook.yml | ||
| LICENSE | ||
| mini_swe_runner.py | ||
| model_tools.py | ||
| package-lock.json | ||
| package.json | ||
| pyproject.toml | ||
| README.es.md | ||
| README.md | ||
| README.ur-pk.md | ||
| README.zh-CN.md | ||
| registration_lifecycle.py | ||
| ruff.pre-commit.toml | ||
| ruff.toml | ||
| run_agent.py | ||
| SECURITY.es.md | ||
| SECURITY.md | ||
| setup-hermes.ps1 | ||
| setup-hermes.sh | ||
| setup.py | ||
| SOUL.md | ||
| toolset_distributions.py | ||
| toolsets.py | ||
| trajectory_compressor.py | ||
| utils.py | ||
| uv.lock | ||
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. In Desktop, choose their provider, model, and limits under Settings → Model → Subagents, then Apply the complete route. Write Python scripts that call tools via RPC, collapsing multi-step pipelines into zero-context-cost turns. |
| Runs anywhere, not just your laptop | Six built-in terminal backends — local, Docker, SSH, Modal, Daytona, and Vercel Sandbox — plus plugin backends such as Singularity/Apptainer. 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
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 source installer delegates Python 3.14, Node.js, npm, ripgrep, FFmpeg, and Python dependencies to PM. If Git is absent, it stages the verified Git for Windows archive in Hermes' tool store. It does not replace your system Git. See installation methods for the separate MSIX/App Installer package and its update ownership.
Android / Termux: A signed APT repository is available for aarch64 devices, with a
stablechannel (tagged releases) and a prereleasecanarychannel. The package includes Python, Node.js, and the TUI. Use the Termux guide, not the desktop/server installer script.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, 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.
Start with the PM developer workflow for activation, daily use, dependency changes, and leaving the environment. Development Setup covers the separate test environment and verification commands.
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.