Hermes Agent introduces self-evolution with a reported 39.5% quality gain

The core release is hermes-agent-self-evolution, which Nous describes as “an evolutionary self-improvement system” for Hermes Agent. In the main announcement, the team says it uses DSPy plus GEPA to optimize “skills, prompts, and code,” maintains populations of solutions, and applies “LLM-driven mutations” aimed at specific failures rather than doing standard model finetuning.

The strongest concrete evidence so far is the phase-one validation result. The results screenshot says the pipeline runs “via API calls without GPU training” and reports a baseline-to-optimized jump from 0.408 to 0.569 on the arXiv skill, labeled as “+39.5%.” Teknium’s linked validation report is the source document for that early measurement, but the public evidence here is still narrow: one skill, one phase, and one reported score delta.

That still makes the release interesting for engineers because the target of optimization is not just prompt text. Nous says the loop can rewrite the agent’s “skills, descriptions, prompts, and code” results screenshot, which pushes it closer to a self-editing agent framework than a prompt tuner.

Hermes’ weekend release bundled several runtime features that make the self-improvement story more relevant to production agents. In the launch thread, Nous says Hermes now supports automatic provider failover when a primary model is rate-limited or down, with fallback switching across providers including Codex OAuth and Nous Portal. The same post also says tool outputs now redact “API keys, tokens, and passwords” across 22-plus patterns before they ever reach model context.

Those surrounding changes matter because self-modifying or self-optimizing agents are only useful if the runtime is resilient. Nous also says Hermes now runs across Signal, iMessage, Telegram, Discord, WhatsApp, Slack, and CLI with “full feature parity” the launch thread, while Teknium adds that the agent supports “locally running models” and can run locally local-run note. Together, that gives engineers a concrete set of patterns to inspect: local execution, fallback routing, memory across sessions, and a search loop that tries to improve an agent’s own components over time.