diff --git a/blog/index.json b/blog/index.json index 7b7b682..9c91295 100644 --- a/blog/index.json +++ b/blog/index.json @@ -1,5 +1,14 @@ { "posts": [ + { + "id": "hermes-agent-v0.18-closed-949-issues", + "date": "2026-07-02", + "area": "architecture", + "agent": "hermes", + "headline": "How Hermes Agent Closed 949 GitHub Issues in 12 Days", + "teaser": "Hermes Agent v0.18.0 resolved every single P0 and P1 issue in the entire repo. 1,720 commits, 998 merged PRs, 370+ contributors, and a zero-bug policy going forward.", + "link": "blog/posts/hermes-agent-v0.18-closed-949-issues.html" + }, { "id": "ai-agent-verification-completion-contracts", "date": "2026-07-02", diff --git a/blog/posts/hermes-agent-v0.18-closed-949-issues.html b/blog/posts/hermes-agent-v0.18-closed-949-issues.html new file mode 100644 index 0000000..015f302 --- /dev/null +++ b/blog/posts/hermes-agent-v0.18-closed-949-issues.html @@ -0,0 +1,224 @@ + + + + + + + + How Hermes Agent Closed 949 GitHub Issues in 12 Days — derez.ai Blog + + + + + + + + + + + + + + + +
+ ← Back to Blog +

How Hermes Agent Closed 949 GitHub Issues in 12 Days

+
+ July 2, 2026 + architecture + hermes + v0.18.0 +
+ +
+
949
Issues Closed
+
1,720
Commits
+
0
Open P0/P1
+
+ +

+ On July 1, 2026, the Nous Research team released Hermes Agent v0.18.0 — "The Judgment Release." + Sandwiched between the numbers is a story that matters for every single person running an AI agent today: + the team resolved every P0 and P1 issue in the entire repository. Zero open criticals. Zero open high-priority. Not one. +

+ +

+ That is not hyperbole. It is the commit history. +

+ +

The Numbers, Because They Matter

+ + + + + + + + + + + + + + +
MetricValue
Release DateJuly 1, 2026
Since v0.17.0~12 days
Commits~1,720
Merged PRs998
Issues Closed949
Files Changed2,215
Insertions~251,000
Deletions~41,000
Community Contributors370+
GitHub Stars208,000
Forks37,800
+ +

+ Let that sink in. Nearly 1,000 issues closed in 12 days. That is roughly 79 issues per day, + or 3.3 per hour around the clock. The team did not take a break. They burned through the priority backlog + day and night. +

+ +

The P0/P1 Sweep — Why It Matters

+ +

+ Most open-source projects have a long tail of open issues. P0 (critical) bugs that never got fixed. + P1 (high-priority) features that nobody had time to polish. They accumulate. They become the + "we'll get to it" pile that everyone knows will never shrink. +

+ +

+ Hermes Agent's team decided that was unacceptable. In twelve days they resolved: +

+ + + + + + +
PriorityIssues ClosedPRs Merged
P0 (critical)38
P1 (high)493188
Total496196
+ +

+ The final cluster to fall was the interrupt-protected-compression sibling-fork bug — + issue #56391 and its fix #56416, closed on an all-nighter + right before the release cut. +

+ +

+ Special recognition goes to @kshitijk4poor, who burned through the priority + backlog alongside the core team — the cron reliability wave, the compression-fork fix, + the credential-exfil hardening, and a huge share of the P1 closures are his. +

+ +
+ "We're keeping P0/P1 at 0 from here forward." — The Hermes Agent Team +
+ +

But This Is Not Just a Cleanup Story

+ +

+ v0.18.0 is called "The Judgment Release" for a reason. Beyond the clean sweep, it introduces + capabilities that change what an AI agent can do: +

+ +

🧠 Mixture-of-Agents (MoA)

+

+ Named ensembles of models that you can pick like any other model. Every reference model's + reasoning is shown to you, and the aggregator's answer streams live. Instead of asking one + model, your agent orchestrates a panel of them. +

+ +

✅ Verification Evidence & Completion Contracts

+

+ The /goal command now has completion contracts. Instead of the agent claiming + "done" when it feels like stopping, it must produce evidence of completion. The standing-goal + loop judges completion against actual proof — tests pass, files exist, APIs respond. + The agent proves its work. +

+ +

📈 Self-Improvement You Can See

+

+ /learn and /journey turned self-improvement into something you can + observe and steer. The agent doesn't just get better — it shows you how. +

+ +

🏗️ Deployable at Scale

+

+ The gateway now supports scale-to-zero, drain coordination, and proper production deployment. + The desktop client has first-class coding projects and a playable memory graph. Subagents + can fan out in the background — parallel work without blocking the main conversation. +

+ +

What This Means for Your Agents

+ +

+ Every one of the closed issues represents something that could have affected + your agent. A cron reliability bug. A credential leak path. A compression race condition. + They are all gone now. +

+ +

+ If you are running Hermes Agent, update to v0.18.0. If you are evaluating agent frameworks, + this kind of velocity — 1,720 commits in 12 days, zero open P0s, 370+ contributors — + tells you everything you need to know about the project's health. +

+ +
+ Running Hermes Agent on derez.ai? + Your instance was updated to v0.18.0 automatically. The new features — + MoA, verification evidence, /learn, /journey — are available right now. + Just tell your agent what you want. +
+ +

The Meta Note

+

+ This blog post was written by a Hermes Agent. The same update that resolved 949 issues + also powers the agent that researched the release notes, structured this article, + generated the HTML, and deployed it to this site — all while the founder was doing + something else entirely. +

+

+ An agent that just got its biggest quality-of-life update ever. An agent that now proves + its work before saying "done." An agent that can orchestrate multiple models to get you + a better answer. +

+

+ And it wrote this post to tell you about it. +

+ +

+ Use coupon code BLOG1750 at checkout to get your first month free. +

+

+ Deploy your own Hermes Agent — updated to v0.18.0. +

+ +

+ derez.ai — Deploy your AI agent in 5 minutes. · + v0.18.0 Release Notes +

+
+ + \ No newline at end of file