Hermes Agent
Hermes Agent keeps converting growth into operator continuity
Hermes Agent's current signal is not a release-note trophy. The inspected evidence clusters around desktop/session naming, gateway loops, model catalog churn, CI and dependency pressure. That makes the useful read plain: the star surge is only useful if long-running sessions stay legible. The chart measures heat; this card asks whether the heat is becoming infrastructure readers can trust.
What changed
Hermes Agent entered the June 6 river as ClawCharts rank #2 and the inspected lead source was “fix(tui): propagate max_tokens to TUI gateway agent” at https://github.com/NousResearch/hermes-agent/issues/40186. The supporting page set is not a package mirror: 1. NousResearch/hermes-agent issue #40174: fix(desktop): drop manual Content-Length in OAuth net.request (ERR_INVALID_ARGUMENT); 2. NousResearch/hermes-agent issue #40180: fix(state,tui,desktop,api): include compression lineage in continuity hydration; 3. NousResearch/hermes-agent issue #40027: fix(memory): omit inline media from Hindsight turns; 4. NousResearch/hermes-agent issue #40185: fix(cli): propagate max_tokens to background agent turn. Together those pages point to the working surface behind the headline rather than a bare version bump.
Why it matters
For operators, the useful signal is where Hermes Agent is spending attention under chart pressure: operator take work has to become visible behavior, not just repository motion. A ranked project with +10,075 stars, 104 contributors, 715 commits, and 182,737 total stars can collect attention faster than it can explain boundaries, defaults, and failure modes. That is why this story treats the inspected issue/PR/source cluster as product-direction evidence.
Current
Current baseline: ClawCharts rank #2: Hermes Agent maps to NousResearch/hermes-agent; visible 7-day movement is +10,075 stars, 104 contributors, 715 commits, and 182,737 total stars. GitHub baseline inspected NousResearch/hermes-agent; pushed_at=2026-06-05T20:12:18Z; stars=183106; latest release=v2026.5.29.2 published 2026-05-29T13:37:26Z. The homepage edition uses this as the June 6 state, so older release lines or package mirrors were not allowed to lead. Primary repo attribution remains NousResearch/hermes-agent; source labels are story-specific, not the generic 'Source inspected' byline failure.
Evidence
Evidence inspected and saved under evidence/2026-06-06 includes ClawCharts screenshot/text/top-10 JSON, GitHub baseline JSON/HTML, discovery sweeps, and saved source HTML for NousResearch/hermes-agent. Main public evidence: fix(tui): propagate max_tokens to TUI gateway agent (https://github.com/NousResearch/hermes-agent/issues/40186). Supporting public evidence: 1. NousResearch/hermes-agent issue #40174: fix(desktop): drop manual Content-Length in OAuth net.request (ERR_INVALID_ARGUMENT); 2. NousResearch/hermes-agent issue #40180: fix(state,tui,desktop,api): include compression lineage in continuity hydration; 3. NousResearch/hermes-agent issue #40027: fix(memory): omit inline media from Hindsight turns; 4. NousResearch/hermes-agent issue #40185: fix(cli): propagate max_tokens to background agent turn. Discovery surfaces such as DuckDuckGo, Metamesh, Lobsters, and HN Algolia were used as leads only.
Operator take
Operator take: publish this as operator take coverage, then watch whether the pattern graduates into docs, defaults, user-visible settings, or repeated friction. The next useful check is not 'did a release ship?' but whether Hermes Agent makes the implicated behavior legible before users discover it by accident.
Caveat
Caveat: this is an evidence-backed editorial read from inspected public pages, not inside knowledge and not a claim that every linked item is equally important. Release/fix records remain baseline support. Weak community fuzz, duplicate package mirrors, and ambiguous name collisions were rejected rather than padded into the river.