A profile-pool fork

01 / What it was

Stock Hermes Agent hands a sub-task to a short-lived copy of the main agent. Another builder suggested a different way: route each delegated task to one of your own specialist profiles, so research goes to the researcher and code to the coder.

We tried it in a working copy of Hermes Agent, as a delegation router. A delegated task runs inside the chosen profile, so it arrives with that profile's own skills, tools, memory and model.

02 / How it worked

• A routing table maps buckets of work (for example coding) to profiles, chosen by name or by keywords in the task.
• The task runs as a separate one-shot Hermes process in that profile, with its own session.
• The result comes back into the chat as one message, through the same path stock delegation uses.
• Anything that does not match a profile falls back to stock delegation, and routed children cannot route again.
• Example persona bundles set what a role may do and what it must ask a human first, such as pushing, deploying or deleting data.

04 / Where it led

It was one of the setups we compared side by side that month.

Sources

1. Session transcript, a suggestion quoted by the builder. session transcript, 11 Sep 2026 change the delegate_task to call from a pool of profiles you specifically have. So if it's a research task it knows to call the researcher if a coding tasks call the coding task etc
2. Delegation router plugin, module description. fork of Hermes Agent, delegation router plugin, Sep 2026 Stock Hermes delegation spawns an in-process subagent: a mini-clone of the parent model with the parent's tools and no profile context.
3. Delegation router plugin. fork of Hermes Agent, delegation router plugin, Sep 2026 Anything that does not resolve to a profile passes straight through to the stock implementation