Agent field guidePersonal agent

Hermes Agent
situationalNous Research · beta · osi-open-source
MIT-licensed personal and super-agent with persistent memory, messaging, schedules, subagents, and a learning loop.
Visit hermes-agent.nousresearch.com →Open in NoemiumSource verified 2026-08-19
ledger entry · observed by @whysanesanders
Hermes combines a broad personal-agent surface with better-than-average approval, pairing, file-safety, and sandbox controls. The learning loop and provider breadth are genuinely differentiated, but a default local terminal backend still shares the user's filesystem authority and the 64K context floor makes small local models a poor fit.
layer
Personal agent
maturity
beta
deployment
local · self-hosted · hybrid
evidence
Source verified
Install
command · Linux, macOS, WSL2, or Android via Termux
curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bashofficial install source →download · Hermes Desktop on macOS or Windows
official install source →Best for
- Provider-neutral personal agents with persistent memory and scheduled work
- Telegram, Discord, Slack, WhatsApp, Signal, or email control of a remote agent
- Operators who want local, Docker, SSH, or cloud sandbox backends
Requirements
- Git; Linux also needs curl and xz-utils before the installer runs
- A model with at least 64,000 tokens of context for agent tool use
- At least one supported subscription, API provider, or local OpenAI-compatible endpoint
Real cost scenarios
Software with a free or existing provider
$0/mo
Hermes software is free; existing hardware and provider access are excluded.
Nous Portal Plus
$20/mo
Current monthly plan includes $22 of portal credits.
Hermes Cloud small instance
$9+/mo
Roughly $0.29 per running day rounded to a 30-day month; inference and tools are extra.
Models and providers
Nous PortalOpenAI and ChatGPTAnthropic and Claude subscriptionsxAI and SuperGrokGitHub CopilotOpenRouterOllama, vLLM, llama.cpp, and other OpenAI-compatible endpoints
Channels and surfaces
terminal TUITelegramDiscordSlackWhatsAppSignalemail
Security boundary
critical privilegeSelected terminal backend, Hermes state directory, messaging channels, and configured model/tool providers.
- The default local backend has the same filesystem access as the operating-system user.
- Keep smart or manual approvals enabled and use Docker or a cloud sandbox for untrusted tasks.
- Pair messaging users, keep allowlists narrow, and never enable an allow-all gateway with terminal access.
Known limitations
- A 64K model context is mandatory for agent tool use.
- The broad feature set and provider matrix create a large configuration surface.
- Smart approvals reduce accidental damage but are not a sandbox against a hostile agent.
- Cloud-instance prices exclude inference and external tool charges.
Typed evidence
- 1Availabilitygithub.com/hermes-agent-org/hermeschecked 2026-08-19
- 2Installhermes-agent.nousresearch.com/docs/getting-started/quickstart/checked 2026-08-19
- 3Requirementshermes-agent.nousresearch.com/docs/integrations/providers/checked 2026-08-19
- 4Pricingportal.nousresearch.com/infochecked 2026-08-19
- 5Pricingportal.nousresearch.com/infochecked 2026-08-19
- 6Licensegithub.com/hermes-agent-org/hermes/blob/main/LICENSEchecked 2026-08-19
- 7Security / threat modelhermes-agent.nousresearch.com/docs/user-guide/security/checked 2026-08-19