# Hermes Super Agent: Hermes Agent plugin

> Lead-Worker Super Agent coordination and turn supervision for long chat turns.

Canonical: https://hermeswatcher.com/plugins/super-agent  
Tier: Community  
Official page (Nous Research): https://hermes-agent.nousresearch.com/docs/plugins/super-agent  
Last updated in catalog: 2026-11-14

Lead-Worker Super Agent coordination and turn supervision for long chat turns. After 60 s in one turn the chat-facing Lead agent is reminded to answer or delegate, and at 120 s editing and execution pause while reads, delegate_task and wrap-up tools stay available; a foreground terminal command running past 30 s is asked to yield to Hermes's background process registry (the same path a mid-turn user message takes) so the turn is released instead of hanging. Each Worker subagent is briefed before it starts with the user's own words, memory and the task ledger; a Worker that returns the same step result repeatedly is stopped, a Worker's open question is carried back to the Lead agent, and a background Worker's result is repeated until the user has seen it. Delegated tasks are recorded in a SQLite ledger that survives gateway restarts. Governance is a positive allowlist: only the platforms named in governed_platforms (default weixin) and the subagents they spawn are affected, and every other surface runs untouched.

## Good to know before installing

Registers hooks for pre_llm_call, pre_api_request, pre_auxiliary_call, post_auxiliary_call, pre_tool_call, post_tool_call, transform_tool_result, subagent_start, subagent_stop, on_session_end, on_session_reset and on_session_finalize, a system-prompt section and a tool_execution middleware, so for governed sessions it can block or amend tool calls and results, LLM request context and subagent handoffs, and asks a governed foreground terminal command still running after 30 s to move to Hermes's background process registry (through core's internal yield flag, which a Hermes release may change); it copies your Hermes USER.md and MEMORY.md memory files in full into every governed delegate_task brief, can start an internal agent turn via inject_message to re-report an unseen subagent result, and writes a local ledger.db under the plugin's Hermes data directory; no network calls, no agent tools, no credentials, no shell commands.

From the plugin's catalog listing.

## How to install

1. Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.

```bash
hermes plugins install super-agent
```

2. Said no? Turn it on later:

```bash
hermes plugins enable super-agent
```

3. Restart Hermes so it loads the plugin.

Some plugins also need a sign-in or settings: see the official page. Memory plugins ask whether to become your memory provider instead. Steps follow the official plugins guide: https://hermes-agent.nousresearch.com/docs/user-guide/features/plugins

## Facts

- Category: Automation & multi-agent, Memory & notes
- Maintained by: JerryLiu369 (Community)
- Needs: No API keys declared
- Requires Hermes: `>=0.22`
- Version: 0.2.0
- In the catalog since: 2026-11-14

## Links

- [Full setup and settings (official page)](https://hermes-agent.nousresearch.com/docs/plugins/super-agent)
- [Source code](https://github.com/JerryLiu369/hermes-super-agent)
- [All plugins](https://hermeswatcher.com/plugins.md)

---

HermesWatcher is an independent guide. It is not affiliated with or endorsed by Nous Research. The [official Hermes Agent documentation](https://hermes-agent.nousresearch.com/docs) and [repository](https://github.com/NousResearch/hermes-agent) from Nous Research are the authority; each page here lists the official sources it was written from. If this site and the official docs disagree, trust the official docs. Index for agents: https://hermeswatcher.com/llms.txt
