Hermes, Six Months Later
A ten-person team spent six months pruning Hermes's memory while its storage kept growing, and the two files they trimmed were capped at under a page each. Find out where the growth likely lives, why nobody can say whether a self-improving agent got smarter or dumber, and the 8-step protocol that gives a human ownership of what it learns.
- 00:00 The Hermes agent and six months of self-improvement
- 01:30 Memory architecture and state database mechanics
- 02:30 Understanding skills and regression task sets
- 03:30 The ten-person team's mysterious storage bloat
- 04:30 Where growth actually lives in the database
- 06:30 The pruning confusion and checkpoint illusion
- 08:30 Specific documented failures in skill evolution
- 10:30 Unmeasured gains versus documented losses
- 11:30 Trace signals as early warning indicators
- 12:30 The release train's escalating safety locks
- 14:00 The curator tool's flawed archival logic
- 15:30 Version change versus memory drift separation
- 16:30 Team scale friction and the corrective ratchet
- 17:00 Deep Seek Harness versus Hermes architecture
- 18:00 Corporate liability and the right to erasure
- 19:00 The only concrete gain: human-imposed structure
- 19:30 Five-step protocol for safe agent operation
- 20:00 The human bottleneck and alert thresholds
- 20:30 Measurement matters more than undo
- 21:00 The adversarial measurement problem
Read transcript
Hermes's two memory files have hard size caps, so the growth is happening somewhere else
A ten-person team pruned Hermes's memory for six months and watched its storage keep growing, and nobody has measured why (Yudame Research (2026). Hermes, Six Months…). That account is a single report nobody has verified. So treat it as a question, not a finding (Yudame Research (2026). Hermes, Six Months…).
Hermes Agent is Nous Research's open-source, MIT-licensed agent. It writes and edits its own skills, keeps a small curated memory and can search its past sessions (Nous Research (2026). Hermes Agent docs: M…). The curated memory is two Markdown files under ~/.hermes/memories/ (Nous Research (2026). Hermes Agent docs: M…). MEMORY.md is capped at about 2,200 characters (about 800 tokens), and USER.md at about 1,375 characters (about 500 tokens) (Nous Research (2026). Hermes Agent docs: M…). Hermes loads both as a frozen snapshot, a fixed copy, at the start of each session (Nous Research (2026). Hermes Agent docs: M…).
So those two files cannot grow without limit. But Hermes writes the full message history to a SQLite database file, ~/.hermes/state.db, plus its WAL and SHM sidecar files, and the docs list no size cap (Nous Research (2026). Hermes developer gui…). Pruning the memory files never touches that database. The docs also warn about "flat installs", where runtime state sits untracked inside the git checkout. That layout makes backups and versioning harder (Nous Research (2026). Hermes developer gui…).
That gives a likely suspect, not a verdict. No public deployment has reported measured store sizes over time. So the idea that state.db caused the team's growth is inferred from how Hermes is built (Yudame Research (2026). Hermes, Six Months…).
MEMORY.md is capped at about 2,200 characters (about 800 tokens), and USER.md at about 1,375 characters (about 500 tokens).
What this means for listeners: Before you prune anything, measure each store in ~/.hermes, because the two capped memory files are the least likely culprit.
The failures have issue numbers, but the gains have no data, and nobody has measured the net
The public record shows specific failures and vague gains, and nobody has measured the balance (Yudame Research (2026). Hermes, Six Months…). Each failure has a GitHub issue number. Issue #67582 asks Hermes to block near-duplicate skills (NousResearch/hermes-agent GitHub issues #6…). In issue #99661, the background skill reviewer flooded the pending queue until 74 changes were waiting for a human. Maintainers closed the issue two days later (NousResearch/hermes-agent GitHub issues #6…).
Issue #35121 says a near-full memory caused a retry loop. It asks that "memory quota exceeded" stop triggering retries (NousResearch/hermes-agent GitHub issue #35…). Release v0.20.0 fixed "ghost skills", deleted skills that still affected sessions (NousResearch/hermes-agent GitHub releases…). And issue #12238, still open, asks for per-skill edit history, memory diffs and single-skill rollback (NousResearch/hermes-agent GitHub issue #12…).
The gains have no numbers behind them. MarkTechPost wrote that the agent "gets smarter the more you use it" but gave no outcome data (MarkTechPost (2026). Coverage of Hermes Ag…). One report describes a resumed session running 581 queued tool calls in under two minutes (Yudame Research (2026). Hermes, Six Months…). The "dumber after a month" reports are second-hand. The research tools could not fetch Reddit, X or Discord (Yudame Research (2026). Hermes, Six Months…).
The one independent study is small. Library Drift, a single May 2026 workshop paper, found that letting skills pile up without retiring them on results leads to retrieval errors and stalled performance (Zhang et al. (2026). Library Drift: Diagno…). But it also found that retiring skills too early does harm. Both effects were small, +0.002 and −0.019, and the paper did not test Hermes (Zhang et al. (2026). Library Drift: Diagno…).
Part of the tilt toward failure is reporting bias. People file issues when things break, not when things quietly work, and memory-provider vendors describe the problem in terms of what they sell (Yudame Research (2026). Hermes, Six Months…). So the evidence neither supports nor refutes the expectation that the agent improves and declines in equal measure (Yudame Research (2026). Hermes, Six Months…).
In issue #99661, the background skill reviewer flooded the pending queue until 74 changes were waiting for a human.
Failures are documented more firmly than gains. Nobody has measured the net effect.
What this means for listeners: Treat both "gets smarter" and "gets dumber" as untested claims until you have your own measurements.
Six months of Hermes releases added brakes on self-editing and loosened none
Over six months, Hermes moved its self-editing features toward human control (NousResearch/hermes-agent GitHub releases…). Version 0.19.0 turned on smart approvals by default. Then v0.21.0 required approval for writes to AGENTS.md, skills and memory, and v0.21.4 added skill pinning (NousResearch/hermes-agent GitHub releases…). Version 0.22.6 added per-skill locks. Version 0.23.0 added a curator lock that holds even in YOLO mode, the most permissive setting, plus admin locks on config keys (NousResearch/hermes-agent GitHub releases…). The docs also describe a memory.write_approval setting (Nous Research (2026). Hermes Agent docs: M…).
The direction is verified, but the motive is not. The August notes name one threat: a prompt-injected agent quietly rewriting its own standing orders. Beyond that, the maintainers published no reason (NousResearch/hermes-agent GitHub releases…). A seatbelt shows that someone worried about crashes, not how many crashes happened.
The Curator is Hermes's main tool against a bloated skill library. It shipped in v0.12.0 on 30 April 2026 and runs on a roughly 7-day cycle. It merges duplicate skills, archives unused ones, and can be reversed with hermes curator rollback (Nous Research (2026). Hermes Curator docs…). Most docs say a skill goes stale after 14 days unused and is archived after 30, but at least one says 30 and 90 days. Issue #79295 says older installs may keep 30/90 after a config migration (Nous Research (2026). Hermes Curator docs…). Nobody has measured how often the Curator merges or archives the wrong skill (Yudame Research (2026). Hermes, Six Months…). And it retires skills by age and use, while Library Drift warns against retiring skills without evidence of how they perform (Zhang et al. (2026). Library Drift: Diagno…).
The release pace is itself a suspect. Hermes shipped about 36 releases in six months, roughly one every 5 days (NousResearch/hermes-agent GitHub releases…). Version 0.22.0 alone reports about 6,080 merged PRs from about 2,520 contributors. Version 0.23.0, released 5 November, was the latest as of 9 November (NousResearch/hermes-agent GitHub releases…). So an agent that "got dumber" may be running different software, not drawing on worse memory (Yudame Research (2026). Hermes, Six Months…). Other fixes in the same months: cron agents now use persistent memory, long-lived gateways release closed sessions' memory, and v0.21.2 added profile isolation (NousResearch/hermes-agent GitHub releases…).
Hermes shipped about 36 releases in six months, roughly one every 5 days.
What this means for listeners: Read your own Curator settings, and assume any change in behaviour could come from a new version until a test rules that out.
Shared corrections and agent-written plugins add risk, but nobody has tested either
No study shows how ten people's corrections interact in one shared skill library (Yudame Research (2026). Hermes, Six Months…). Issue #88429 describes a "corrective ratchet": one user's correction after a bad day hardens into a permanent rule for everyone (NousResearch/hermes-agent GitHub issue #88…). Across ten people, conflicting rules could leave an agent that hedges, asks for too many confirmations or behaves inconsistently (Yudame Research (2026). Hermes, Six Months…). That mechanism is reasoned from one open issue, not measured. Hermes has had profile isolation since v0.21.2. Nobody has verified whether a shared gateway cleanly separates each person's memory (NousResearch/hermes-agent GitHub releases…).
DeepSeek Harness (DSH) puts the risk in a different place. It is DeepSeek's MIT-licensed desktop agent, built on the Cordis framework, where tools, skills and even the interface are plugins (deepseek-ai/deepseek-harness GitHub reposi…). Every release is a developer-preview pre-release with warnings about breaking changes. The latest is v0.2.2-rc.1 from 4 November 2026, and the project has less than about three months of public history (deepseek-ai/deepseek-harness GitHub reposi…). Its Creator mode lets the agent write, install and test a plugin from a chat request (DeepSeek (2026). DeepSeek Harness official…). A plugin is executable code, so one bad plugin can do more damage than one bad Hermes skill, which is a Markdown file (Yudame Research (2026). Hermes, Six Months…). Hermes drifts through many small, silent changes, and DSH through fewer, larger ones. DSH's official materials document no user-facing undo (Yudame Research (2026). Hermes, Six Months…).
The security and legal commentary is early, and it comes from one research tool that relied on vendor blogs (Vendor and practitioner commentary on the…). That tool reads Article 14 of the EU AI Act as saying that clicking "Accept" on every prompt is not enough oversight (Vendor and practitioner commentary on the…). It also flags a clash between the GDPR right to erasure and audit logs that cannot be edited. Its proposed fix, separate logs, has not been validated by any regulator (Vendor and practitioner commentary on the…). The named incidents, such as Plugin4Shell, and a 0.00% scanner detection figure were not independently verified (Cloud Security Alliance and vendor blogs o…). The same commentary says deployers carry the liability, and that running a developer preview in production weakens their position. It cites no case law (Vendor and practitioner commentary on the…).
One user's correction after a bad day hardens into a permanent rule for everyone.
What this means for listeners: Limit each correction to the person or task it came from, and treat any agent-written plugin as untested code.
Improvement shows up when a human owns what the agent learns
The one concrete gain on record came from structure that a human imposed, not from the agent improving itself (Practitioner blog (June 2026). Restructuri…). A June 2026 practitioner blog described moving from "60 skills flat, no quality control" to layered hubs with rules for merging and retiring skills (Practitioner blog (June 2026). Restructuri…). The research tools agree on the governance advice below. But that advice is judgment, and no study shows it improves outcomes (Yudame Research (2026). Hermes, Six Months…). Here is a protocol built from it:
- Measure the size of each store in ~/.hermes today, then weekly for 4 weeks, then monthly. Flag any store that grows more than 20% in 4 weeks or passes 1 GB (Yudame Research (2026). Hermes, Six Months…).
- Commit memories and skills at least daily to a git repository the agent cannot change. Gitignore state.db*, auth.json and .env, as the docs advise (Nous Research (2026). Hermes developer gui…). Run hermes backup weekly, and test a restore within 2 weeks (Yudame Research (2026). Hermes, Six Months…).
- Build a set of about 30 real tasks. Run it weekly for 8 weeks against a clean profile, with no learned memory or skills, and against the live profile (Yudame research digest (Claude run, 2026)…). Investigate if the live pass rate falls 10 percentage points or more (Yudame Research (2026). Hermes, Six Months…).
- Pin the Hermes version, upgrade at most every 2–4 weeks, and run the task set in staging first. Prefer the stable pipeline that began with v0.21.6 (NousResearch/hermes-agent GitHub releases…).
- Turn on memory.write_approval and lock skills you curated by hand. Have a named owner review the pending queue twice a week, with an alert above 20 items (Yudame Research (2026). Hermes, Six Months…).
- Check your Curator thresholds. Retire a skill on results, for example after 10 logged uses with less than 50% success (Yudame Research (2026). Hermes, Six Months…).
- Audit standing rules every 4 weeks, and limit each correction to one person or task (Yudame Research (2026). Hermes, Six Months…).
- Run DSH Creator mode only in a sandbox, and have a person review every plugin the agent writes (Yudame Research (2026). Hermes, Six Months…).
One research digest proposes tiers of autonomy. The agent saves low-risk notes automatically, an owner reviews drafts, shared skills need human approval, and credentials, permissions and plugin installs are never automatic (Yudame research digest (Claude run, 2026)…). Also track tokens, retries and skills loaded per task. In Library Drift, these trace-level signals changed before the end-task scores did (Zhang et al. (2026). Library Drift: Diagno…).
Build a set of about 30 real tasks and run it weekly for 8 weeks against a clean profile and the live profile.
Parameters come from the consensus advice above. They are judgment, not outcome-tested.
What this means for listeners: Give the agent's learning a named owner, a weekly task test and a pinned version before you trust either verdict.
- Nous Research (2026). Hermes Agent docs: Memory (MEMORY.md and USER.md caps, frozen snapshot, write_approval)
- Nous Research (2026). Hermes developer guide: session storage, session-storage recovery, profile distributions, updating (state.db, gitignore advice, flat installs)
- Yudame Research (2026). Hermes, Six Months Later: ground-truth research report and cross-model synthesis, 9 Nov 2026
- NousResearch/hermes-agent GitHub issues #67582 (19 Jul 2026) and #99661 (31 Aug 2026), as cited in a single research report
- NousResearch/hermes-agent GitHub issue #88429 (17 Aug 2026): the corrective ratchet
- NousResearch/hermes-agent GitHub issue #35121 (30 May 2026): memory-quota retry loop
- NousResearch/hermes-agent GitHub issue #12238 (18 Apr 2026): per-skill history and memory diffs
- NousResearch/hermes-agent GitHub releases, v0.12.0 to v0.23.0 (Apr–Nov 2026)
- Nous Research (2026). Hermes Curator docs and GitHub issue #79295 on 30/90 versus 14/30 defaults
- MarkTechPost (2026). Coverage of Hermes Agent: 'gets smarter the more you use it'
- Practitioner blog (June 2026). Restructuring 60 flat skills into layered hubs with merge and retire rules
- Zhang et al. (2026). Library Drift: Diagnosing and Fixing a Silent Failure Mode in Self-Evolving LLM Skill Libraries, arXiv 2605.19576 (ICML FAGEN workshop)
- deepseek-ai/deepseek-harness GitHub repository, README and releases (to v0.2.2-rc.1, 4 Nov 2026)
- DeepSeek (2026). DeepSeek Harness official page: Creator mode
- Vendor and practitioner commentary on the EU AI Act, GDPR Art. 17 and SOC 2 for agents (via Gemini research digest, 2026)
- Cloud Security Alliance and vendor blogs on semantic supply-chain attacks (via secondary sources, unverified)
- Reddit r/hermesagent roundups and practitioner anecdotes (second-hand, unverified)
- Yudame research digest (Claude run, 2026). Tiered-autonomy proposal and 30-task regression set with clean-profile baseline