Hermes Agent v0.18.0 — The Judgment Release

Source: raw/reddit-1ukxez2.md (r/hermesagent, u/Jonathan_Rivera, posted 2026-07-01) cross-checked against the official GitHub release notes (github.com/NousResearch/hermes-agent/releases) on 2026-07-02. The release, the “Judgment Release” name, the Mixture-of-Agents provider change, and the commit/contributor tallies are confirmed by the official notes; only the P0/P1-subset item counts remain community-reported. Update via hermes update.

Hermes Agent v0.18.0 (“The Judgment Release”, 2026-07-01) is reported as a stabilization-focused release: over roughly 12 days the team closed every open P0 and P1 issue and PR — a “clean sweep” of the highest-priority backlog — and promoted Mixture-of-Agents (MoA) from a config toggle to a first-class model provider. Where v0.17 “The Reach Release” widened Hermes’s external contact surfaces, v0.18 turns inward to triage and deliberation — the “Judgment” name plausibly nods both to the backlog purge and to MoA’s council-style aggregation. ^[inferred: theme interpretation not stated in the source] The release, its name, the MoA-as-provider promotion, and the headline commit and contributor numbers are confirmed against the official GitHub release notes (cross-checked 2026-07-02); only the P0/P1-specific item counts remain community-reported.

Key Takeaways

• P0/P1 clean sweep (confirmed release theme). Over ~12 days the team closed every open P0 and P1 issue and PR. The ~692 highest-priority items (496 issues + 196 PRs) is the P0/P1 subset; across the whole window the official notes report 949 issues and 998 PRs closed in ~1,720 commits from 370+ contributors (207k stars). The team committed to keeping P0/P1 at zero going forward.
• Final P1 closed at the wire. The last P1 was an interrupt-protected-compression sibling-fork bug (#56391), closed just before the release cut.
• Mixture-of-Agents is now first-class. MoA moved from a config toggle to a dedicated moa provider, shown alongside Claude, GPT, and Grok in every model picker — CLI, TUI, desktop, and gateway.
• Per-sub-agent visibility. Pick a named council (e.g. “my-council”) the same way you would pick any single model, and you see each sub-agent’s contribution.
• Confirmed against the official notes. The release, name, MoA change, and the commit/contributor/star tallies are corroborated by the official GitHub release page (cross-checked 2026-07-02). The P0/P1-subset counts and the #56391 attribution remain single-community-sourced.
• More than MoA and the sweep. The official notes also ship self-verification against evidence, /goal completion contracts, /learn + /journey, a scale-to-zero and drain-coordinated gateway, desktop coding projects plus a playable memory graph, background subagent fan-out, Vertex AI as a first-class provider, and /prompt ($EDITOR). See “Beyond MoA and the sweep” below.

The P0/P1 Clean Sweep

The headline claim is a full triage of the highest-priority backlog:

• Over roughly 12 days, the team reports closing every open P0 and P1 issue and PR.
• The purge totals ~692 highest-priority items — 496 issues plus 196 PRs.
• The work landed as ~1,720 commits from 370+ contributors.
• The final P1 to close was an interrupt-protected-compression sibling-fork bug (#56391), cut right before release.
• The team states an ongoing commitment to keep P0/P1 at zero after this release.

The commit and contributor tallies (1,720 commits, 370+ contributors) and the overall 949-issues / 998-PRs window are confirmed by the official GitHub release notes. The 692-item P0/P1 subset split (496 issues + 196 PRs) and the #56391 attribution remain community-reported; treat those two as reported rather than measured.

Mixture-of-Agents Is Now First-Class

The second headline change promotes MoA into the provider layer:

• Before: MoA presets were a configuration toggle — an opt-in ensemble mode buried in settings.
• Now: MoA appears as its own moa provider, listed alongside Claude, GPT, and Grok in every model picker across the surfaces — CLI, TUI, desktop, and gateway.
• You pick a named council (the post’s example is “my-council”) exactly the way you would select any single model.
• The provider exposes per-sub-agent visibility — you see every sub-agent’s contribution to the aggregated answer, rather than an opaque blended output.

This change also refreshes what the wiki already documents about the MoA ensemble in Plans; MoA-as-a-provider is a surfacing/UX promotion of the existing ensemble capability rather than a new algorithm. ^[inferred: the source describes only the surfacing change, not new MoA internals]

Beyond MoA and the sweep

The official release notes list several features the initial community summary omitted:

• Self-verification. The agent now checks its own work against evidence rather than “vibes” before declaring a task done.
• /goal completion contracts. Goals can carry explicit completion criteria the agent must satisfy before a goal is considered done.
• /learn and /journey. Self-improvement is made visible and steerable, so you can see and direct what the agent learns.
• Gateway deployable at scale. Scale-to-zero plus drain coordination make the gateway production-deployable.
• Desktop: coding projects and a playable memory graph. The desktop app gained first-class coding projects and an interactive memory-graph view.
• Background subagent fan-out. Subagents can now run in the background instead of blocking the main turn.
• Cheaper self-improvement. The post-turn self-review loop routes to an auxiliary model instead of re-burning the main model’s context.
• Vertex AI as a first-class provider. Auto-mints and refreshes GCP service-account OAuth2 tokens, so Gemini-via-Vertex sessions no longer expire mid-run.
• /prompt. Opens $EDITOR for drafting long prompts in real markdown.
• Security hardening. Credential-exfiltration protection and input sanitization across provider boundaries.

Try It

1. hermes update to v0.18, then read the full changelog on GitHub (github.com/NousResearch/hermes-agent/releases) and confirm the v0.18.0 tag.
2. Open any model picker (CLI, TUI, desktop, or gateway) and select the moa provider to run a Mixture-of-Agents council instead of a single model.
3. Configure or select a named council (e.g. “my-council”) and inspect each sub-agent’s contribution per turn to compare against a single-model run.
4. (Maintainers / watchers) Check the P0/P1 queue on GitHub to confirm the zero-backlog claim and see whether “keep P0/P1 at zero” holds after the release.

Related

• Hermes Agent v0.19 — The Quicksilver Release — the successor; where v0.18 cleared the backlog and promoted MoA, v0.19 turns to latency (~80% TTFT cut), credential integration, and a durable delivery ledger.
• Hermes Agent v0.17 — The Reach Release — the immediate predecessor in the release line; v0.18 turns from external reach to internal triage.
• Plans — already documents the MoA ensemble; the new moa provider refreshes it.
• Hermes Multi-Agent Workflow Template — multi-agent orchestration context for how MoA councils fan work across sub-agents.
• Hermes Architecture Explained — where providers and the model picker sit in the overall stack.
• Hermes Agent — topic index.

Open Questions

• The overall figures (~1,720 commits / 370+ contributors / 949 issues + 998 PRs / ~12 days) are now confirmed against the official GitHub release notes. The 692-item P0/P1 subset split (496 issues + 196 PRs) and the #56391 “last P1” attribution remain single-community-sourced; spot-check those two before citing as measured.
• The v0.18.0 date-based tag is 2026.7.1 (confirmed on the official releases list), consistent with the prior “v0.NN.0 plus vYYYY.M.D” pattern.
• Whether the “keep P0/P1 at zero” commitment holds after release is worth re-checking on a later refresh.