🎩 Role split
Orchestrator = judgment
The orchestrator owns the task framing, picks what to delegate, and decides what to trust. It is the one with the holistic view.
👋 Hermes agents explainer
Meet the Minions.
Keep the brains in charge.
In Hermes, a minion is a separate helper session launched by an orchestrator agent. The orchestrator keeps the big picture, then spins up minions to research, inspect, click through pages, summarize, compare options, or handle repetitive work without cluttering the main thread.
Scoped context
Cheap delegation
Clean isolation
Fast feedback loops
Role: scout, mechanic, critic
Context: only what it is given
Output: report back, don’t take over
At a Glance
Think of the setup as a tiny crew. A human or outside trigger asks for something. The orchestrator decides what matters, breaks the work into parts, and launches minions with tightly scoped instructions. Those minions do bounded work and return results. The orchestrator checks the output, merges the useful bits, and presents a coherent answer.
Operator
Sets goal or asks the question
Orchestrator
Plans, delegates, verifies, synthesizes
Minions
Run isolated subtasks with scoped tools
Payoff
Less clutter, lower cost, tighter control
🎬 Meet the Crew
👤
You / Human
Asks the big question
🎩
Orchestrator
Plans & decides what to delegate
🛠️
Minions
Scout, mechanic, librarian, skeptic
✨
Result
Clean answer, no mess
How Hermes Agents Are Structured
A minion is not just a mood. It is a separate conversation session created through delegate_task or a comparable orchestration path. It gets its own instructions, its own context bundle, and its own tool permissions.
🚪 Isolation
Minion = bounded execution
A minion sees only the packet it was given. That keeps side quests, irrelevant pages, and low-value noise out of the main context.
📝 Prompt packet
Instructions are explicit
The orchestrator can pass files, URLs, error text, constraints, output format, and tool limits. If a minion needs something, it has to be handed over directly.
💸 Spend discipline
Model choice can vary
Cheap minions can do broad, repetitive, or low-risk work. Stronger models can be reserved for synthesis, debugging, or judgment-heavy decisions.
🕶️
The fun version: the orchestrator is the director, and the minions are the sharply dressed field crew. They do the legwork; they do not become the boss.
What Happens When a Minion Launches
1
🎯 Goal arrives. The orchestrator receives a task: inspect a page, summarize a file set, compare options, test a flow, or draft a first pass.
2
🔪 Task gets sliced. The orchestrator decides whether the job is better as one focused pass or several smaller subtasks.
3
📋 Instruction packet is built. The packet includes the goal, relevant context, tool restrictions, and the exact shape of the result expected back.
4
🚀 Minion runs in isolation. It uses only the granted tools and context. No ambient mind-reading, no hidden shared memory, no magical leakage from the parent.
5
📤 Result returns upward. The orchestrator checks the result, verifies risky claims when needed, and folds the useful pieces into the final answer.
6
🏁 Session ends. The minion's job is done. It is disposable by design, which is part of why the main thread stays cleaner.
Where Instructions Come From
Minions do not invent their own mission. Their behavior comes from layered instructions, each with a different purpose.
| Layer | What it does |
|---|---|
| System prompt | Defines the broad role, safety boundaries, and tool behavior expectations. |
| Task goal | States what this minion is supposed to accomplish right now. |
| Context packet | Provides the relevant file paths, URLs, error messages, notes, or summaries. |
| Tool scope | Limits the minion to the specific toolsets needed for the job. |
| Return format | Tells the minion how to report back so the orchestrator can use the result cleanly. |
🤓
Beginner note: Think of instructions like a mission briefing. The orchestrator writes the brief — the minion just follows it. If a minion seems confused, the fix is better briefing, not smarter vibes. Check the packet first.
💡
Key principle: if the orchestrator does not pass the context, the minion does not know it. That explicitness is what keeps delegation legible.
Types of Agents in Hermes
🎩 Main lane
Primary orchestrator
Owns the relationship with the user, holds the overall plan, and decides when to delegate.
🛠️ Worker lane
Leaf minions
Focused helpers that do one thing well: search, inspect, summarize, verify, click through a flow, or analyze a document.
⚙️ Structured lane
Specialized subagents
Purpose-built variants for code review, QA, data collection, browser inspection, or research synthesis.
Why Use Minions at All
🧹 Cleaner main thread
Less context sludge
Instead of stuffing every URL, console log, and dead end into the main chat, the orchestrator gets back a compact answer.
⚡ Parallelism
More things can happen at once
Independent subtasks can be split across multiple minions instead of forcing one long serial chain.
💰 Cost control
Cheap models for cheap jobs
Bulk reading, preliminary sorting, or repetitive scraping can run on lower-cost models while judgment stays with the main agent.
🛡️ Trust boundaries
Verification is easier
Because minion outputs come back as bounded reports, the orchestrator can check important claims before presenting them as truth.
Minion Playbook
A fun site deserves fun roles, but the roles should still map to useful behaviors. Here is a simple playbook for how a minion crew can be thought about.
🔍 Scout
Find the terrain
Search widely, pull candidate sources, skim quickly, and bring back the shortlist worth deeper attention.
🔧 Mechanic
Touch the system
Run commands, inspect logs, test a page, or follow an interaction path while the orchestrator watches from above.
📚 Librarian
Organize the mess
Summarize long docs, cluster notes, compare versions, and turn scattered material into a compact brief.
🎭 Skeptic
Try to break the answer
Challenge assumptions, verify claims, test edge cases, and catch places where the first pass sounds better than it is.
Cost Control in Practice
| Job shape | Good delegation choice |
|---|---|
| Read 40 pages and pull recurring themes | Cheap minion first, stronger orchestrator later for synthesis |
| Inspect a live page and list visible controls | Browser-capable minion with narrow scope |
| Judge whether a change is safe or a claim is trustworthy | Keep final judgment with the orchestrator |
| Break work into two unrelated research threads | Use parallel minions, then merge results |
Verification and Trust
Minions are useful, but they are still agents making claims. Treat their summaries as reports, not holy writ.
👍 Good habit
Verify external side effects
If a minion says it uploaded a file, changed a page, or created an artifact, check the returned path, URL, ID, or status.
📸 Good habit
Use evidence-bearing outputs
Ask for screenshots, paths, excerpts, IDs, or structured summaries rather than vague "it worked" language.
⚠️ Watch for
Overconfident synthesis
A clean summary can hide shaky evidence. The orchestrator should still sanity-check what matters.
🍽️ Watch for
Context starvation
If a minion looks confused, the usual fix is not "smarter vibes." It is a better packet: better files, better constraints, better examples.
Quick Glossary
🎩 Orchestrator
The main agent that owns the relationship, plans the task, and decides what to delegate.
🛠️ Minion
A bounded helper session created to do a specific subtask with limited context and tools.
📦 Context Packet
The files, URLs, notes, and instructions passed to a minion when it is launched.
🔒 Scoped Tools
A restricted toolset granted to the minion so it can do the job without unnecessary access.
🧩 Synthesis
The step where the orchestrator combines minion outputs into a final, user-facing result.
✅ Verification
The practice of checking whether a minion's claims are backed by evidence before treating them as settled fact.
📋 Minion Cheat Sheet
🎯 The Roles
🔍Scout — find useful stuff
🔧Mechanic — do the hands-on work
📚Librarian — organize & summarize
🎭Skeptic — check & challenge
⚡ Key Rules
📦Minion only knows what it is given
🚫It can't access the main chat on its own
📝Better packets = better results
✅Always verify side effects