Jonathon's AI Wiki

Hermes Agent v0.18.0 — The Judgment Release

5 min read

Source: raw/reddit-1ukxez2.md (r/hermesagent, u/Jonathan_Rivera, score 117, posted 2026-07-01 — a community-authored “NEWS & UPDATES” release summary, not an official changelog). Every concrete figure below should be cross-checked against the GitHub release (github.com/NousResearch/hermes-agent) before quoting in production. 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] Because the details come from a single community post, treat the specifics as reported rather than confirmed.

Key Takeaways

  • P0/P1 clean sweep (reported). Over ~12 days the team says it closed every open P0 and P1 issue and PR — ~692 highest-priority items (496 issues + 196 PRs) across ~1,720 commits from 370+ contributors — and 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.
  • Provenance caveat. Single community source (u/Jonathan_Rivera), not a first-party changelog — cross-check all figures and the issue number against the GitHub release before relying on them.

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.

All of the above is reported by a community poster, not published as an official changelog — verify the counts, the commit/contributor tallies, and the #56391 attribution against the GitHub release page before citing them as 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]

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.

Open Questions

  • The figures (692 items / 496 issues / 196 PRs / ~1,720 commits / 370+ contributors / ~12 days) and bug #56391 come from one community post — spot-check each against the GitHub release before quoting in production.
  • Prior Hermes releases carry both a “v0.NN.0” name and a date-based tag (e.g. v2026.6.19 for v0.17); the v0.18.0 date-tag was not captured at ingest. ^[inferred: pattern from prior releases]
  • Whether the “keep P0/P1 at zero” commitment holds after release is unverified and worth re-checking on a later refresh.

Graph View

Backlinks