Hermes BibleUnofficial Docs
← All flows Flow / Configuration

10 Real Hermes Agent Settings That Actually Matter

A no-nonsense rundown of the real Hermes configuration that moves the needle — identity, memory, profiles, cron, gateway, MCP, skills, context files, delegation, and plugins. Real config keys and commands only, no made-up env vars.

Hermes AgentMCPXsettingsactuallymatterno-nonsenserundownconfigurationmoves
Category
Configuration
Level
Community
Author
Tony
Reading time
5 min

A no-nonsense rundown of the real Hermes configuration that moves the needle — identity, memory, profiles, cron, gateway, MCP, skills, context files, delegation, and plugins. Real config keys and commands on...

Community flow by Tony. View source

Flow sections

Section outline mirrored from the public community flow. Use the source page for full prose and examples.

Upstream outline

  1. Why this list exists
  2. 1. SOUL.md — the thing that gives Hermes a spine
  3. Style
  4. Technical posture
  5. 2. Memory config — because forgetting everything is embarrassing
  6. 3. Profiles — because one Hermes for everything turns into a mess
  7. 4. Cron scheduling with --deliver — where chat turns into operations
  8. 5. Gateway — because your agent shouldn't be trapped in a terminal
  9. 6. MCP servers — the cleanest way to bolt Hermes onto the rest of your stack
  10. 7. Skills — where Hermes stops solving the same problem from scratch
  11. 8. Context files — so the project doesn't need a full re-explanation every time
  12. 9. Subagent delegation — the thing that makes one agent feel like five
  13. 10. Plugins — where the extension system gets fun
  14. The actual lesson

Section map

Why this list exists

Frames why this list exists for this Configuration workflow, including the operating context to verify in the source page.

1. SOUL.md — the thing that gives Hermes a spine

Frames 1. soul.md — the thing that gives hermes a spine for this Configuration workflow, including the operating context to verify in the source page.

Style

Frames style for this Configuration workflow, including the operating context to verify in the source page.

Technical posture

Frames technical posture for this Configuration workflow, including the operating context to verify in the source page.

2. Memory config — because forgetting everything is embarrassing

Frames 2. memory config — because forgetting everything is embarrassing for this Configuration workflow, including the operating context to verify in the source page.

3. Profiles — because one Hermes for everything turns into a mess

Frames 3. profiles — because one hermes for everything turns into a mess for this Configuration workflow, including the operating context to verify in the source page.

4. Cron scheduling with --deliver — where chat turns into operations

Frames 4. cron scheduling with --deliver — where chat turns into operations for this Configuration workflow, including the operating context to verify in the source page.

5. Gateway — because your agent shouldn't be trapped in a terminal

Frames 5. gateway — because your agent shouldn't be trapped in a terminal for this Configuration workflow, including the operating context to verify in the source page.

Implementation notes

  • Use this Configuration flow as a pattern library entry: start from the summary, then inspect the linked source before copying any commands, schedules, or account wiring.
  • Primary decision areas: Why this list exists, 1. SOUL.md — the thing that gives Hermes a spine, Style, Technical posture, 2. Memory config — because forgetting everything is embarrassing. Treat those sections as checkpoints for scope, cost, orchestration, and human review.
  • Useful search signals for this flow: settings, actually, matter, no-nonsense, rundown. These are derived from the public title and summary, not from private runtime data.

Decision table

Best fitConfiguration workflow pattern

Use when the summary outcome matches your own workflow and why this list exists is relevant to your setup.

Verify firstAccounts, models, schedules, and tool access

Open the source sections for Why this list exists and 1. SOUL.md — the thing that gives Hermes a spine before wiring credentials or automation.

Review boundaryHuman approval point

Keep human approval for merges, spending, external messages, credentials, and unattended execution.

Verification checklist

  1. Confirm the workflow outcome matches your use case: A no-nonsense rundown of the real Hermes configuration that moves the needle — identity, memory, profiles, cron, gateway, MCP, skills, context files, delegation, and plugins. Real config keys and commands only, no made-up env vars.
  2. Open the source section for Why this list exists before copying commands, prompts, or schedules.
  3. List every credential, account, model, and external service the flow would touch.
  4. Define the human approval step before spending money, sending messages, trading, merging, or running unattended.
  5. Run a small dry run and compare the result with the source sections for Why this list exists and 1. SOUL.md — the thing that gives Hermes a spine.

Risk notes

Automation

Start with a bounded dry run, logs, and a manual stop path before enabling recurring or unattended execution.

External messages

Keep human review before sending public posts, customer messages, trading instructions, or team notifications.

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • A no-nonsense rundown of the real Hermes configuration that moves the needle
  • identity, memory, profiles, cron, gateway, MCP, skills, context files, delegation
  • plugins. Real config keys
  • commands only, no made-up env vars.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page