Skip to main content
9 – 17 UHR +49 8031 3508270 LUITPOLDSTR. 9, 83022 ROSENHEIM
DE / EN
Coding agent Nous Research Terminal, IDE, Messaging

Hermes Agent

Hermes Agent is Nous Research's open-source, self-improving AI agent harness with memory, skills, a messaging gateway and free model choice.

Licence MIT
Interfaces Terminal (CLI), Desktop app, IDE (VS Code, Zed, JetBrains via ACP), Messaging gateway (per the documentation, 20+ platforms incl. Telegram, Discord, Slack, WhatsApp, Signal, Microsoft Teams)
Platforms macOS, Linux, Windows, Termux/Android
Instruction file AGENTS.md

The seven building blocks in Hermes Agent

How Hermes Agent implements the building blocks of an AI harness

  1. 1

    Agent loop

    A synchronous conversation loop in the `AIAgent` class (`agent/conversation_loop.py`) handles provider selection, prompt construction, tool execution, retries and context compression, per the architecture docs.

  2. 2

    Tools and execution environment

    More than 40 built-in tools plus MCP servers give access to files, web search, browser automation and image generation; commands run locally, in Docker, over SSH, or in cloud sandboxes such as Daytona and Modal.

  3. 3

    Context management

    Of the project context files `AGENTS.md` or `HERMES.md`, Hermes Agent loads only the one with the highest priority per session, per the documentation, walking from the working directory up to the git root; `SOUL.md` is loaded independently and globally from the Hermes home directory. Skills load their full content only when needed, per the documentation, to keep the context window lean.

  4. 4

    State and memory

    `MEMORY.md` and `USER.md` store bounded memory (about 800 and 500 tokens respectively) across sessions; `session_search` additionally full-text searches all past CLI and messaging conversations.

  5. 5

    Permissions

    A tiered security model with Smart, Manual and Off approval modes governs risky commands; a fixed blocklist stops irreversible actions regardless of YOLO mode, per the documentation.

  6. 6

    Verification and feedback

    `/undo` and `/retry` roll back individual turns; a batch runner and cron jobs enable repeatable, unattended automations with delivery to messaging channels, per the documentation.

  7. 7

    Orchestration

    Via `tools/delegate_tool.py` the agent can spawn isolated subagents for parallel workstreams, which return a condensed result to the main context.

Models and model access

Which models the harness uses and how they are obtained

Models and model access
Models model-agnostic - any LLM via a provider or a custom endpoint
Access routes Nous Portal, OpenRouter, Anthropic, OpenAI, Google Gemini/Vertex, AWS Bedrock, Azure AI Foundry, custom OpenAI-compatible endpoints (Ollama, vLLM, SGLang, llama.cpp, LM Studio)
Free choice of model Yes
Custom endpoint / LLM gateway Yes
Custom endpoints can be set interactively via `hermes model`, or directly in `~/.hermes/config.yaml` via `provider: custom` and `base_url`.
Features
MCP servers Sub-agents Skills Plugins / extensions Sandbox Headless / CI SDK IDE integration Checkpoints Resume sessions
Running it with herdr
Supported by herdr Yes
State detection Screen manifest
Integration Session
Per herdr's support table, herdr detects Hermes Agent only through the terminal screen manifest, without additional state integration via lifecycle hooks.
More about herdr →

Enterprise use

Data processing, controls and pricing model according to the vendor

Data processing and custom endpoints

Model access runs either through cloud providers or fully self-hosted endpoints such as Ollama, vLLM or LM Studio; with a custom endpoint, source code stays within the environment you configure yourself.

Access via messaging gateways

DM pairing with time-limited codes and allowlists such as `GATEWAY_ALLOWED_USERS` govern, per the security documentation, who can reach the agent through Telegram, Slack and other platforms; a central enterprise SSO is not documented there.

Admin policies

Approval modes, a fixed blocklist for irreversible commands, and an optional write-safe root (`HERMES_WRITE_SAFE_ROOT`) constrain, per the documentation, what the agent can execute automatically.

Telemetry and supply chain

The security documentation makes no statements about telemetry or usage-data collection; a built-in scanner checks for known-compromised Python packages at startup, per the documentation.

Pricing model

Hermes Agent itself is open source with no licence cost; the optional Nous Portal access bundles model access and extra tools on a subscription or usage basis via your own API keys.

Strengths
  • Self-improving skills that automatically distil repeated tasks into reusable procedural knowledge
  • Seven execution backends from local to cloud sandbox with serverless persistence
  • One gateway for, per the documentation, 20+ messaging and chat platforms with continuity across sessions
  • Model and provider freedom, including self-hosted OpenAI-compatible endpoints
  • A tiered security model with granular approval rules for risky commands
Limitations
  • Per the documentation, programmatic integration runs through several protocols (ACP, TUI gateway JSON-RPC, an OpenAI-compatible HTTP API) rather than a single, uniformly packaged SDK
  • No central enterprise identity management (SSO) described in the public documentation

Use cases

Typical tasks for this harness

A personal AI agent with memory for developers and technically inclined users
Automated, recurring tasks via cron jobs delivered to messaging channels
Coding and DevOps tasks via terminal, Docker and SSH backends
A remotely reachable agent via Telegram, Slack or Discord while on the move

AI harnesses are the software layer that makes a language model capable of acting. Hermes Agent is Nous Research’s open-source AI harness: a self-improving AI agent with persistent memory that runs in the terminal, as a desktop app, in IDEs and through messaging platforms, and works with nearly any language model. As of 20 September 2026.

What is Hermes Agent?

Hermes Agent is developed by Nous Research, a research lab that also publishes the Hermes model family. The project is open source on GitHub at NousResearch/hermes-agent under the MIT licence. On Linux, macOS, WSL2 and Termux it is installed via curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash; native Windows uses a PowerShell one-liner. Afterwards, hermes starts an interactive conversation. Besides the terminal interface, Hermes Agent offers a desktop app, an ACP integration for VS Code, Zed and JetBrains, and a gateway that, per the documentation, connects to 20+ messaging and chat platforms, including Telegram, Discord, Slack, WhatsApp, Signal and Microsoft Teams.

Hermes Agent as an AI harness

Technically, a synchronous agent loop (the AIAgent class) drives the cycle of provider calls, tool execution and context compression - the same class serves the CLI, gateway, ACP integration and batch processing, per the architecture documentation. Tools range from file access to web search and browser automation, and can be extended with any MCP server. What stands out is the skills system: for recurring tasks, the agent automatically writes SKILL.md files into ~/.hermes/skills/, improves them with use, and loads their full content only when needed - compatible with the open agentskills.io standard. Risky commands are governed by a tiered approval model (Smart, Manual, Off) with a hard-coded blocklist for irreversible actions such as rm -rf /. For parallel workstreams, the agent can spawn isolated subagents via tools/delegate_tool.py. Per the documentation, a Python plugin system covers custom tools, providers, memory backends and read-only observer hooks for telemetry; for external programs, the Agent Client Protocol (ACP), a JSON-RPC gateway protocol and an OpenAI-compatible HTTP API (gateway/platforms/api_server.py) are additionally available for programmable integration.

Models and model access

Hermes Agent is deliberately model-agnostic: hermes model switches between Nous Portal, OpenRouter, Anthropic, OpenAI, Google Gemini, AWS Bedrock, Azure AI Foundry and self-hosted options such as Ollama or vLLM. For a custom endpoint, set provider: custom and base_url under model: in ~/.hermes/config.yaml, or choose “Custom endpoint” interactively in hermes model. Because this freely configurable OpenAI-compatible endpoint is documented, model access can generally be routed through a central proxy such as our AI Gateway by entering its endpoint as base_url.

Enterprise use: data protection and governance

The security documentation describes a layered model of approval modes, blocklists, container isolation for the Docker backend, and SSRF protection for web tools. It does not address telemetry or central usage-data collection, and no enterprise SSO is documented; instead, DM pairing codes and allowlists govern access via messaging channels. Importantly for practice: source code, file contents and prompts go to whichever model provider is configured - with cloud providers, that means outside your own environment. This belongs in your records of processing activities in advance, regardless of whether Hermes Agent runs locally or on a server.

Orchestrating Hermes Agent with herdr

herdr is a terminal runtime that supervises several coding agents at once. Per herdr’s documentation, it detects Hermes Agent through the terminal screen manifest and provides session integration through it - deeper state integration via lifecycle hooks is not currently documented for Hermes Agent. Teams running several terminal agents in parallel can fold Hermes Agent into the same overview as other supported harnesses this way.

Where it fits: developer harness and enterprise harness

Hermes Agent is primarily a personal, self-improving agent for developers and technically inclined users - with a terminal, IDE integration and its own messaging channels. For business users across an entire company who don’t work from a terminal, CompanyGPT is the fitting harness: tools via MCP servers and integrations, roles from Entra ID or Keycloak, and audit logs for governance. Our AI Gateway provides the shared cost and governance layer across different harnesses and model providers. For an overview of other agent harnesses, see our harness overview. If you’d like to check how a self-improving agent like Hermes Agent fits securely into your existing system landscape, we’re glad to help with selection and hardening.

From developer harness to enterprise harness

Coding harnesses are tools for developers. Business users, cost control and governance need two more layers.

CompanyGPT – the harness for business users

CompanyGPT gives any language model tools via MCP servers, integrations and n8n, company knowledge via companyRAG, roles from Entra ID or Keycloak, and audit logs – operated in your Azure environment or sovereignly on STACKIT.

Discover CompanyGPT
AI Gateway – cost and governance for every agent

The AI Gateway bundles the model access of your tools and coding agents behind an OpenAI-compatible API: authentication via Entra ID, budgets and cost centres per team, user and agent, guardrails and complete logging.

View the AI Gateway

Frequently Asked Questions

What is Hermes Agent?

Hermes Agent is an open-source AI agent harness from Nous Research with a built-in learning loop: it creates its own skills from experience, improves them with use, and retains knowledge across sessions. It runs in the terminal, as a desktop app, in IDEs via ACP, and through messaging platforms.

Is Hermes Agent open source?

Yes. The `NousResearch/hermes-agent` repository is licensed under the MIT licence according to GitHub, and its source code and documentation are freely accessible.

Which models does Hermes Agent support?

Hermes Agent is model-agnostic and can be switched via `hermes model` to Nous Portal, OpenRouter, Anthropic, OpenAI, Google, AWS Bedrock, Azure AI Foundry, or a custom OpenAI-compatible endpoint - with no code changes.

Does Hermes Agent work with herdr?

Yes. herdr detects Hermes Agent through the terminal screen manifest and provides session integration; deeper state integration via lifecycle hooks is not documented for Hermes Agent in herdr's support table.

What sets Hermes Agent apart from classic coding agents like Claude Code?

Classic coding harnesses are built around a single repository and terminal. Hermes Agent extends that pattern with persistent memory, self-improving skills, a cron scheduler and messaging gateways, so the same agent keeps working outside a single coding project too.

Can Hermes Agent be used in a GDPR-compliant way?

That depends on the chosen model provider and where it runs: a self-hosted endpoint operated locally or in the EU can narrow data processing, but the public documentation makes no fixed GDPR commitments for the harness itself. Review data processing and data flows in your own records of processing activities beforehand.

Introduce coding agents safely in your company

We support selection, model access in the EU, permission design and cost control.