Field guide / primary domain

Hermes Agent

22

sources in this field

Updated July 16, 2026

Current thesis

The shortest path to orientation.

Hermes from Nous Research crossed from model into full agent OS with discovery, distribution, coordination, and maintenance layers. Core agent converts every action into reusable self-improving skill and runs on Codex CLI/GPT-5.5 backend subsidizing 24/7 deploy/ops generalist for $100/month; given GitHub, SSH, Cloudflare tokens it one-shots local projects to live (domain+DNS+SSL+nginx+PM2). Hermes Workspace consolidates chat, memory, skills, terminal, files into command center; 12+ swarms described as "singularity" performance. Hermes Curator runs weekly consolidating/pruning agent-created skills by usage analytics while preserving externally installed, built-in, pinned skills. Hermes Atlas is community-curated quality-filtered directory of 100+ tools/skills/plugins with live GitHub data. v0.12.0 "Curator Release" added Kanban-based multi-agent coordination: agents claim tasks, work parallel, hand off when blocked, replacing multi-terminal mess with single dashboard; Hermes autonomously planned and produced video about own capabilities. Discord intake bridge: plain-English commands flow into Hermes Kanban (execution engine), tasks mirror back to Discord board. Complete production workflow: deploy on Hetzner/DO/Hostinger VPS with GPT-5.5 fast mode (no reasoning); add Gbrain or custom QMD+SQL memory vault; access via Orca IDE on any device with Tailscale; conduct deep research before projects, run /grill-me uncovering unknowns, iterate until evals pass capturing learnings. Key discipline: monitor task duration, stop mid-session requesting status if taking too long. AgentCookie syncs browser sessions between daily Mac and dedicated MacMini agent via Tailscale peer-to-peer, keeping Hermes already logged into services. Integration maturity gates adoption. Setup path: connect Google Workspace first (without Gmail/Calendar/Drive/Docs/Sheets agent cannot manage workflow); use Firecrawl as default web search (cleaner data, fewer tokens) plus Browserbase for full browser automation; use Composio for one-click integration (hours to minutes); place Hermes on private Tailscale-connected device network. Community self-documents—use cases scraped from X, GitHub, Reddit, HN, YouTube, blogs, podcasts into shared resource of what people actually build. Recipe—personal agent + workspace UI + automated skill curator + community discovery + shared task board—is template other ecosystems converge on. Documentation lags: community requesting authoritative cheatsheet signals active usage paired with DX maturation gaps. Research-agent recipe (pick domain, give sources, define signal, save evidence, deliver daily briefs, give plain-English feedback) lives in autoresearch.

Evidence board

Claims worth carrying forward
01

Hermes's self-improving skill loop produces measurable compounding: one Sr AI Architect reported 40% less task time on domain-similar tasks after accumulating 20+ skills. A competitive briefing shrank from 20 min to 8 min over 6 weeks with the same prompt — improvement came from skill accumulation, not prompt changes.

02

Token cost structure is severely skewed: profiling a Hermes v0.6.0 deployment across Telegram + WhatsApp + Cron gateways showed 73% of every API call is fixed overhead. A $5 VPS playbook warns that default setup can produce a $400 OpenRouter bill; skill-cached runs were ~63% cheaper than re-derivation.

03

24/7 Hermes on a Mac Mini for 2 months with 18 cron jobs, 35 scripts, 6 custom skills ran at $21/month total. A separate user built a two-tier email pipeline (pure Python tier-1 for state, LLM tier-2 only on new mail) to achieve zero LLM calls when inbox is idle.

04

A self-learning weather trading bot turned $100 into $216 in 48 hours: Hermes scans weather markets every 60 min, compares 3 forecast sources per location, buys undervalued temperature buckets, reviews outcomes, and writes its own strategy notes. A separate no-code Polymarket bot applies Kelly Criterion position sizing via plain-English prompts.

05

After ~15 tool calls setting up a Prometheus/Grafana monitoring pipeline, Hermes unprompted entered a reflection phase and generated a skill at ~/.hermes/skills/devops/monitoring-pipeline/SKILL.md — adjusting variables per new context rather than template reuse. This autonomous skill generation is the mechanism behind the compounding efficiency gains.

06

Nous Research's own team runs 12 Hermes instances in parallel daily: backend team monitors/investigates stack issues, post-training team creates RL environments, benchmarks, and directly manipulates datasets. Hermes has reached top-100 GitHub repositories of all time.

07

One builder spent 200–400 hours (3 failed attempts totaling 149 hours) building a memory kernel: L1 Hindsight, L2 Graphiti, L3 MemPalace. A separate $200/30-skills personal analyst setup uses a Reflect skill that synthesizes past info, connects relationships, and surfaces Top 5 Daily Insights — showing that memory architecture is the hardest and highest-leverage customization layer.

08

Compounding autonomy carries compounding risk: one challenge entrant reported a $47 surprise bill from an overnight run. Skill rot and trust surface expansion are identified failure modes alongside cost drift — compounding autonomy is described as 'a property you manage, not just enjoy.'

Adjacent fields

Key voices

Latest evidence

Recent additions

All synthesized insights →

Nous Research

Hermes Agent: 262 Community Use Cases Across 15 Categories

Nous Research's Hermes Agent page aggregates 262 real-world deployments scraped from X, GitHub, Reddit, HN, YouTube, and Discord. Stories span dev workflows, personal assistants, trading bots, enterprise deployments, and self-hosted setups — revealing Hermes as a general-purpose agent OS with self-improving skills, three-layer memory, and natural-language cron as its signature primitives.

JUMPERZ

Hermes Kanban + Discord Orchestration Layer

A two-layer agent workflow: Discord handles plain-English commands and task visibility (especially mobile), while Hermes Kanban is the execution system that assigns, tracks, runs, logs, and proves work. An intake bridge connects both, creating Discord commands → Hermes tasks → Discord task board mirroring.

Shann³

How to Become a Hermes Agent Operator

Comprehensive operator guide for Hermes Agent by Nous Research—an open-source autonomous agent framework with 150K GitHub stars and #1 OpenRouter usage. Covers architecture (brain/personality/skillset), four-level deployment progression (laptop to full VPS fleet), multi-agent control room patterns, a 21-step SEO pipeline, and the prototype→production methodology for marketing automation.

Garry Tan

Garry Tan's Agent-Building Loop: Skillify, Cron, Evals, Repeat

Garry Tan describes a repeatable 4-agent build pattern: do a task manually, skillify it, schedule via cron, verify it's resolvable, add evals and integration tests, then repeat. The quoted framing treats agent failures as organ failures rather than model failures—memory, actions, and self-check are separate subsystems to diagnose and patch independently.

Alex Finn

Codex Remote Network: One Dev Machine, Many Control Nodes

Alex Finn's workflow uses one always-on Mac (Mac Studio) as the sole code-writing machine, with all other devices (iPad, iPhone, additional Macs) acting as remote command nodes via Codex's 'control this Mac' / 'control other devices' settings plus Tailscale for a private mesh network. The claimed result is location-independent coding from any device worldwide.

Jonata Santos

Full-Stack Personal Agent Workflow with Hermes, GBrain, and Orca

A concrete personal-agent stack: Hermes on a VPS (Hetzner/DO/Hostinger), GBrain or QMD+SQL memory vault, GPT-5.5 fast mode via Codex auth, Orca IDE on macOS/iOS via Tailscale. The workflow gates every project with deep research, `/grill-me` unknowns surfacing, written evals, and iterative runs until all evals pass — saving learnings to the vault throughout.

OpenAI Developers

Codex Record & Replay: Converting Demos into Reusable Skills

OpenAI's Codex gains a Record & Replay feature that lets users demonstrate a recurring workflow once—such as filing expense reports or submitting time-off requests—and have Codex convert that demonstration into an inspectable, editable skill. The user controls recording start/stop.