Hermes Agent Adds Asynchronous Subagents, So Delegated Work No Longer Blocks the Parent Chat

Nous Research has shipped a change to Hermes Agent. Its delegate tool can now run subagents asynchronously. Per the announcement, delegated work no longer blocks the parent chat.

Hermes Agent is an open-source personal agent from Nous Research. A parent agent can spawn child agents, called subagents, to fan out work. Until now, that delegation made you wait.

The update was announced on X by Nous Research and co-founder Teknium. Existing users enable it by running hermes update .

Hermes Agent now supports asyncronous subagents! The existing delegate tool, which your agent uses to spawn subagents to fan out and do work, no longer blocks your chat! To access now, `hermes update`, and enjoy! pic.twitter.com/6hN94wpRLW

The delegation tool is delegate_task . It spawns a subagent, which is an isolated child agent. Each child gets its own conversation, terminal session, and toolset.

Only the final summary returns to the parent. The parent’s context never sees the child’s intermediate tool calls or reasoning. That keeps the parent’s context window small.

Isolation is strict. Subagents start with a completely fresh conversation. They have no knowledge of the parent’s history. The parent must pass everything through the goal and context fields.

Subagents inherit the parent’s API key, provider configuration, and credential pool. That credential pool enables key rotation on rate limits. You can route subagents to a cheaper model through config.yaml .

In source, delegate_task is synchronous. The parent blocks inside the tool call until every child completes. Your chat stays frozen during that wait.

That design prevented several workflows. You could not start a long agent and keep working. You could not check in on a run or steer it mid-flight.

Nous built the non-blocking path in the open. Issue #5586 adds an async_delegation toolset. It spawns a background agent and returns a task_id immediately. The announcement confirms async subagents are now available.

The async tools cover the full lifecycle:

Background agents run as in-process threads. They reuse the same AIAgent machinery, credentials, and toolsets as delegate_task .

A synchronous batch spawns children in parallel and waits. Concurrency is capped by delegation.max_concurrent_children , which defaults to 3.

The async toolset from issue #5586 returns control immediately.