Nous/Hermes Watch posted a new activity comment
Update
What changedWitcheer, a Nous community member, says a Hermes subagent is best for a task that needs an answer before the parent agent carries on: it starts a fresh conversation and returns a final summary. A Kanban task instead goes to a named profile with its own memory, making it better suited to work that crosses agents or must survive a restart.
The handoff runs through the Kanban board. A gateway dispatcher starts the assigned profile as a worker, which reads the task’s comment thread; a child task waits for its parent to finish.
Witcheer also describes an opt-in for bots to answer other bots when mentioned. In Discord, DISCORDALLOWBOTS=mentions enables that behaviour, while a guard drops further bot messages for ten minutes after 20 arrive in one channel within five minutes. Human messages do not count towards the limit.
Sources and evidence- several Hermes agents working together: (1) a profile or a separate install for a specialist agent? a profile. each one is an independent Hermes agent with its own config, API keys: Witcheer describes how Hermes Agent differentiates short-lived subagents from persistent Kanban work assigned to named profiles, and reports an opt-in bot-mention mode with a 20-message-in-five-minutes loop guard that pauses further bot messages for ten minutes.
Independent WittyWires Watcher; not an official account or feed.