Hermes Agent
Hermes proposes one activity board across gateways and profiles
A Hermes Desktop proposal gathers active conversations from local, SSH, URL and cloud gateways into one board. Reply and Stop remain tied to the selected conversation’s owner; related file-navigation proposals preserve the distinction between local and remote paths.
The proposed Agents board changes the unit of attention from a selected chat to a collection of independently owned conversations. A person running several gateways should be able to see which one is waiting for clarification without opening each connection in turn. The existing delegated-worker tree remains a separate tab; it does not pretend to be the complete inventory.
The proposal’s important constraint is that aggregation must not erase ownership. Same-ID sessions on different gateways are treated as distinct, actions carry the exact owning connection and profile, and an optional metadata failure must not redirect a resume. Older gateways without the read-only overview endpoint remain visible with an update notice rather than falling back to list routes that may archive or repair state. Looking at a parked runtime is explicitly not supposed to start it.
The facts
- PR #103954 groups conversations into Needs you, Working, Unread and Idle, rather than showing only delegated subagents. - Finished conversations fade from the activity view after 15 minutes; running or waiting sessions remain regardless of age. - Open, Reply and Stop use the row’s connection, profile and durable session identity, not the foreground gateway. - The proposed collector budgets 12 seconds per source and retains last-known rows as stale when a gateway goes offline. - PR #103953 hides local open/reveal verbs for remote files, while PR #103951 leaves Windows drive-path linkification outside its scope.
Why it matters
A multi-agent dashboard becomes dangerous when ‘Stop’ means whichever machine happens to be in the foreground. This design instead treats the overview as a projection over existing owners. It also distinguishes incomplete inventory from an empty workload: slow sources get a budget, offline sources retain stale rows, and unstable pagination is not labelled complete just because a row count looks plausible. Those choices matter more than the number of cards a dashboard can display.
Current
Inspected on 2026-09-06. The Hermes Agent stable-release baseline is v2026.8.31 published 2026-08-31T19:29:49Z. The main source was open when captured. Release metadata is a version boundary, not evidence that an open proposal has shipped.
Evidence
The primary source is NousResearch/hermes-agent PR #103954 (https://github.com/NousResearch/hermes-agent/pull/103954). Supporting context comes from NousResearch/hermes-agent PR #103951 (https://github.com/NousResearch/hermes-agent/pull/103951); NousResearch/hermes-agent PR #103953 (https://github.com/NousResearch/hermes-agent/pull/103953). The linked records were inspected directly; related project records are not independent confirmations.
Operator take
Test colliding session IDs across two gateways, stop one gateway mid-refresh, and act on a row from the other connection. The proposed author test uses that shape, but readers should verify it on their own build. Related path-link and preview-menu work shows the same product direction: make results easier to reach without making a remote path impersonate a local file. A copy-path action is safe to expose where Finder or File Explorer cannot actually reach the target.
Caveat
All three records were open at inspection. The board and file-navigation work are proposals, not a tagged-release guarantee. Reported browser and test-suite results belong to the contributors; this curation did not run their branches.
All three records were open at inspection. The board and file-navigation work are proposals, not a tagged-release guarantee. Reported browser and test-suite results belong to the contributors; this curation did not run their branches.