AgentsAutonomy & tool use
Nous Research releases Advanced Delegation plugin that lets Hermes Agent send each subagent task to a different model or profile
Nous Research's official Advanced Delegation plugin for Hermes Agent 0.22.5 and later lets the main agent send each subagent task to a model route or Hermes profile that the operator defines. Simple, hard and private work can then run on different models.
From the r/AISEOInsider (via last30days) article of October 27, 2026 and cited sources: The plugin adds two modes to subagent delegation, and only one can be active at a time. [5] [8] [9]
SOURCES[5] advanced-delegation · Plugin Catalog (Nous Research) hermes-agent.nousresearch.com[8] hermes-official-plugins/advanced-delegation · GitHub github.com[9] Nous Research on X x.com
AI-assisted, not human-edited. Methodology Corrections Who owns this site
- What happened
- The plugin adds two modes to subagent delegation, and only one can be active at a time. [5] [8] [9]
- Original source
- r/AISEOInsider (via last30days) article, independent perspective
- Brief by
- AT Pulse research desk AI-assisted; publisher and contact on the desk page
- When
- October 27, 2026 article published
- Covered
- Oct 28 edition
- Evidence
- 14 sources across 8 sites
- 1Hermes Delegation Config: Cut Your Agent Costs in 5 Minutesreddit.com
- 2New Hermes Delegation Update: AI Agent Teams!reddit.com
- 3Hermes Agent Just Got Smarter at Managing AI Teams!reddit.com
- 4Linked video: Hermes Delegation Config: Cut Your Agent…youtube.com
- 5advanced-delegation · Plugin Catalog (Nous Research)hermes-agent.nousresearch.com
- 6Hermes Agent changelog · gradually.aigradually.ai
RisingHow it’s measured
YouTube video · 1.9K views · 10 likes
Reach blends public engagement (views, likes, comments, shares, stars) from the platforms where the story or its original source lives: YouTube, Hacker News, GitHub, Substack and similar. A video and the article written from its transcript share one score, taken from the video. Platforms with no data are left out rather than counted as zero, and the age of a story never lowers its score.
The plugin adds two modes to subagent delegation, and only one can be active at a time. In model routes, each named route (such as fast, deep or local) maps to a model plus either a provider or an OpenAI-compatible endpoint. In profile routes, the subagent runs as an approved Hermes profile with that profile's own model, credentials and skills. The main agent picks a route by reading one-line descriptions, and each result reports which route, provider and model handled it. [5] [8] [9]
The agent sees only route names and descriptions. It never sees model IDs, endpoints or keys, and Hermes rejects any route that isn't on the list before the subagent starts. Profile routes are the exception to this isolation: listing a profile gives subagents that profile's credentials, SOUL.md instructions and terminal access. [5] [4]
For developers, plugins register a delegation provider that either returns a route for a task or raises an error that stops only that task. The route options are added to the tool schema in a fixed order, so the prompt cache stays valid. A mode switch therefore takes effect at the next /new session, unless the user passes --now and accepts one cache break. [10] [8] [11]
Documented: routing per task, limited to approved routes, with credentials hidden from the agent. What follows: teams can move routine or sensitive subagent work to cheaper or local models.
Read the full assessment
They still need to measure savings themselves and treat profile routes as handing over privileges.
The research is finished; the dossier is below.
Executive brief
Nous Research's official Advanced Delegation plugin for Hermes Agent lets the main agent send each subagent task to a different model or Hermes profile. The cost logic is simple: cheap tasks no longer have to run on the expensive model. The agent picks routes only from an operator-written list and never sees model IDs, endpoints or keys (Plugin Catalog). No source measures cost savings. The "cut your agent costs" headline comes from a marketing channel selling a paid community, and no independent evaluation exists.
Read the full section
Nous Research's official Advanced Delegation plugin for Hermes Agent lets the main agent send each subagent task to a different model or Hermes profile. The cost logic is simple: cheap tasks no longer have to run on the expensive model. The safety point matters more. The agent picks routes only from an operator-written list and never sees model IDs, endpoints or keys (Plugin Catalog). No source measures cost savings. The "cut your agent costs" headline comes from a marketing channel selling a paid community, and no independent evaluation exists.
What changed and event timeline
Hermes v0.22.0 ships
Nous's "Threshold Release" adds live views of running subagents in the CLI, TUI and Desktop app. This set up the delegation changes that followed ().
23: The plugin lands
A marketing blog says it reached the official plugins repo on 22 October (). The catalog lists v1.0.0 as pinned on 23 October ().
Hermes 0.22.5 releases
The plugin's README calls this the first release with pluggable delegation providers, which the plugin needs (;).
Nous announces it on X
The post says the orchestrator can pick a different model or profile for each subagent from routes the user sets up ().
Commentary posts appear
The Reddit article and its linked video present a five-minute setup and promote a paid "AI Profit Boardroom" (;).
Capabilities and access
- Model routes (
model_map): named routes such as fast, deep or local. - Profile routes (
profile_routes): a subagent runs as an allow-listed profile with that profile's own model, credentials, skills and SOUL.md. - Only one mode is active at a time. An optional default route handles tasks the agent doesn't route.
Read the full section
- Model routes (
model_map): named routes such as fast, deep or local. Each has a description, a model and either a provider or abase_url. Optional settings:reasoning_effort,service_tier,fallback_providers(Catalog). - Profile routes (
profile_routes): a subagent runs as an allow-listed profile with that profile's own model, credentials, skills and SOUL.md. - Only one mode is active at a time. An optional default route handles tasks the agent doesn't route.
- Install:
hermes plugins install advanced-delegation. Requires Hermes ≥0.22.5. Versions 0.22.0–0.22.4 refuse the install; versions before 0.22.0 load it but do nothing (README). - Runs on Linux, macOS and Windows.
Technical analysis for researchers and developers
- Provider API: plugins register with
ctx.register_delegation_provider().route_task(task, config)returns a route dict or raisesDelegationRouteError. - Schema:
delegate_taskgains an enum (optionorprofile) built from route names in config order (Docs search summary). - Prompt cache: schema parameters must be deterministic.
Read the full section
- Provider API: plugins register with
ctx.register_delegation_provider().route_task(task, config)returns a route dict or raisesDelegationRouteError. A refusal stops only that task, not the others (Developer guide). - Schema:
delegate_taskgains an enum (optionorprofile) built from route names in config order (Docs search summary). - Prompt cache: schema parameters must be deterministic. A mode switch takes effect at
/newunless the user passes--now, which costs one cache break (README; video 06:18). - Model choice: the LLM selects the route from free-text descriptions. No router is trained or evaluated.
- Tests: the repo ships a pytest suite.
Claims and evidence
- Allow-listing and hidden credentials: both appear in Nous's own documentation (Catalog). The video makes the same point (02:14).
- Per-result route metadata: results report route, provider, model, effort and speed tier (Catalog). The auto-captions say "region" where the docs say reasoning effort (02:46).
- "Way more done for way less tokens": this is the presenter's assertion with no data behind it (08:34). The README makes no cost claims.
Read the full section
- Allow-listing and hidden credentials: both appear in Nous's own documentation (Catalog). The video makes the same point (02:14).
- Per-result route metadata: results report route, provider, model, effort and speed tier (Catalog). The auto-captions say "region" where the docs say reasoning effort (02:46).
- "Way more done for way less tokens": this is the presenter's assertion with no data behind it (08:34). The README makes no cost claims.
- Independent check: the reviewed sources contain no independent benchmark or cost audit. The two other Reddit posts come from the same subreddit and poster, so they are not corroboration.
Context and prior work
- Before the plugin, all subagents shared one delegation model or the parent's model.
- A community plugin already offered tiered per-call model selection through
delegate_task_pro(rriggs/delegation-pro). - Research on learned routing has measured savings. RouteLLM (ICLR 2025) reported more than 2× cost reduction without quality loss on public benchmarks (arXiv).
Read the full section
- Before the plugin, all subagents shared one delegation model or the parent's model. By default, up to 10 subagents run in parallel, each with a 250-iteration cap (Delegation patterns).
- A community plugin already offered tiered per-call model selection through
delegate_task_pro(rriggs/delegation-pro). - Research on learned routing has measured savings. RouteLLM (ICLR 2025) reported more than 2× cost reduction without quality loss on public benchmarks (arXiv). Advanced Delegation does something different: it relies on rules the operator writes as route descriptions, with no learned router.
Limitations, safety and contested findings
- Listing a profile gives subagents that profile's keys, SOUL.md and terminal access.
- Keys placed directly in routes are stored in plain text in
config.yaml. - Delegation lives inside the running process. Closing the session,
/stopor a restart can cancel subagent work (Delegation patterns).
Read the full section
- Listing a profile gives subagents that profile's keys, SOUL.md and terminal access. The docs say to list only profiles you are comfortable sharing (Catalog; video 04:27).
- Keys placed directly in routes are stored in plain text in
config.yaml. - Delegation lives inside the running process. Closing the session,
/stopor a restart can cancel subagent work (Delegation patterns). - How well routing works depends on how clear the descriptions are. The presenter suggests a one-week audit of which route each task took (09:09).
- Sources disagree on the release date: 22 October (blog) versus 23 October (catalog).
Business and practitioner implications
- Cost controls and data-residency controls now work at the level of individual subagent tasks.
- Start with two routes, fast and deep, and make fast the default. Then use the route metadata in results to see where spend goes.
- No published numbers exist for this plugin.
Read the full section
- Cost controls and data-residency controls now work at the level of individual subagent tasks. A "local" route keeps sensitive work on an OpenAI-compatible endpoint you run yourself.
- Start with two routes, fast and deep, and make fast the default. Then use the route metadata in results to see where spend goes.
- Measure your own savings. No published numbers exist for this plugin.
- Treat profile routes as granting privileges, and review them with the same care.
The source trail.
Sources (14)
Hermes Delegation Config: Cut Your Agent Costs in 5 Minutes
Feed excerpt only. A transcript of the video linked from this page is supplied (linked video auto captions; https://www.youtube.com/watch?v=K5EUy5Wc_GI); automatic text may contain errors.
reddit.comNew Hermes Delegation Update: AI Agent Teams!
Related coverage; assess separately
reddit.comHermes Agent Just Got Smarter at Managing AI Teams!
Related coverage; assess separately
reddit.comLinked video: Hermes Delegation Config: Cut Your Agent Costs in 5 Minutes
linked video auto captions
www.youtube.com