Hermes Agent
Hermes Agent turns the growth spike into continuity chores
Hermes Agent owns the week’s growth number and is spending that attention on operator continuity: desktop launch identity, gateway behavior, UI rendering, dependency hygiene, and the places where provider and terminal surfaces have to feel less improvised.
What changed
The rendered ClawCharts board now has Hermes Agent at rank #2, and inspected project pages show the day’s signal running through concrete operator surfaces rather than a bare release line. Main inspected source: fix(desktop): single instance, model picker, and theme boot (https://github.com/NousResearch/hermes-agent/pull/43457). Supporting inspected pages include fix(desktop): single instance, model picker, and theme boot, feat(feishu): add interactive card buttons for clarify prompts, fix(gemini): preserve terminal stream finish reasons, feat(feishu): auto-convert markdown tables to native table component, feat(hindsight): make prefetch join timeout configurable.
Why it matters
Hermes Agent owns the week’s growth number and is spending that attention on operator continuity: desktop launch identity, gateway behavior, UI rendering, dependency hygiene, and the places where provider and terminal surfaces have to feel less improvised. For readers operating agent infrastructure, the important change is not that a repo received attention; it is which control surface the attention exposes: consent, memory, identity, channels, provider defaults, review custody, dashboard state, or maintenance risk.
Current
Current baseline: ClawCharts rank #2 on 2026-06-11; +10955 stars over seven days; 112 active contributors; 831 seven-day commits; 189782 chart stars; GitHub repo NousResearch/hermes-agent shows 189957 stars, 19856 open issues, pushed_at=2026-06-11T00:43:24Z; latest release v2026.6.5 published 2026-06-06T00:55:58Z. The repository description observed from GitHub says: The agent that grows with you. Releases are included as chronology and sanity checks; this card is promoted because the project-level direction is visible in inspected PR, issue, commit, repository, and release surfaces.
Evidence
Evidence saved under evidence/2026-06-11 includes clawcharts-top10.png, clawcharts-body.txt, clawcharts-top10.json, github-baseline.json, discovery-surfaces.json, fetched GitHub HTML pages, and public verification artifacts. Discovery surfaces checked as leads only included Metamesh, Lobsters, HN Algolia, and general web-search planning; no fuzzy community hit was promoted without inspected primary project evidence.
Operator take
Publish as a operator-take card. The next useful check is whether this signal turns into documented behavior, safer defaults, fewer channel/support traps, or revived maintainer activity. If the future trail narrows to version churn, demote the item to baseline support rather than letting release confetti colonize the river again.
Caveat
This is a source-transparent operator read, not a claim of complete coverage. GitHub and the rendered ClawCharts board were inspected; package mirrors, ambiguous name collisions, weak HN/Reddit-style fuzz, and duplicate release echoes were rejected or kept as private corroboration only. Main public source label: NousResearch/hermes-agent PR #43457.