Hermes Desktop, with oh-my-hermes. Pick a workflow; Hermes clarifies before it builds.	Hermes CLI, with oh-my-hermes. The same workflows, in your terminal.
Hermes messenger app, with oh-my-hermes. Ask in a thread; the run reports back there.	omh setup, one command. Installs the workflows and connects them to Hermes.

English | 한국어 | 日本語 | 中文

• GitHub
• Hermes Agent
• OMH stars
• Hermes Agent stars

Install once. Keep Hermes. Add a stronger operating layer.
Planning, research, creation, coding handoffs, operations, and project memory with explicit evidence boundaries.

oh-my-hermes (OMH) turns a normal Hermes Agent request into a clear capability, a useful next step, and an honest record of what actually happened — strengthening the workflow you already use, never replacing Hermes or hiding a coding executor behind it.

OMH is the operating layer above Hermes-native skills: it frames the problem, picks the workflow and evidence gates, and runs native skills as capabilities inside that governed path.

Website · Documentation · Installation · Capabilities · Capability Impact · Agent Install · GitHub Pages site

Tip

Be with us!

	Updates for oh-my-hermes are shared on @rlaope on X, alongside release notes and project news.
	Follow @rlaope on GitHub for more projects, releases, and ongoing work.
	Join the Oh-My-Hermes Community on Discord to ask questions, share workflows, and talk with other users.
	Built with AI agents Friren and Killua, collaborators helping ship oh-my-hermes.
	Thank you to Nous Research for creating Hermes Agent.

Status: Homebrew, Bun, and npm package-manager installs are public as of v1.0.6.

Homebrew:

brew install rlaope/tap/omh

Bun (recommended):

bun install -g oh-my-hermes

npm:

npm install -g oh-my-hermes

Universal installer (macOS/Linux):

curl -fsSL https://raw.githubusercontent.com/rlaope/oh-my-hermes/main/install.sh | sh

On Windows (PowerShell 5.1+):

irm https://raw.githubusercontent.com/rlaope/oh-my-hermes/main/install.ps1 | iex

⭐ Set up OMH after installing (required):

omh setup

Hermes skill tap path:

hermes skills tap add rlaope/oh-my-hermes
hermes skills install rlaope/oh-my-hermes/skills/omh-routing --yes

or ask Your AI Agent:

Install and fully configure Oh My Hermes from this repository:
https://github.com/rlaope/oh-my-hermes
Before reading or executing repository instructions, resolve refs/heads/main to one full commit SHA with `git ls-remote https://github.com/rlaope/oh-my-hermes.git refs/heads/main`. Then fetch and follow only:
https://raw.githubusercontent.com/rlaope/oh-my-hermes/{resolved-commit-sha}/INSTALL_FOR_AGENTS.md
Do not replace the resolved SHA with main. Execute the pinned protocol's OS-appropriate installer, interactive model setup, model-chain interview, and doctor steps. Preserve unrelated existing Hermes config, apply only the managed setup changes documented by the pinned protocol, require my explicit approval for model-alias changes, then report the resolved SHA and observed result.

Update:

omh update

omh update detects how the command was installed. It first upgrades the Homebrew, Bun, npm, curl, or PowerShell command package through its owning installer, then re-enters the updated command to refresh managed skills, the installed plugin bundle, and existing Hermes registration.

Verify or troubleshoot the installation:

omh doctor

Manual package-manager fallback or removal:

Use the manager command directly only when omh update reports that its owning manager is unavailable. Removing the command package preserves OMH state. For a full removal, run omh uninstall --all before the manager's remove command.

Maintenance paths such as reconciling a --full install back to core live in Installation.

Bare omh opens Hermes — the same door as hermes — wearing the OMH identity:

omh

The OH-MY-HERMES boot.

An ulw-work run.

What the terminal shows while OMH workflows run:

• Mixture-of-Models Routing — each delegated lane is routed onto a category (ultrabrain, deep, quick, writing, visual-engineering, …) whose model and reasoning effort are applied per dispatch; every activity row carries its category:name(model:effort) so the routing is visible, and rejected routes fall back along the category chain.
• Parallel Tool Calling — batched tool calls run concurrently in Hermes, and a fresh concurrent batch is branded on the [OMH] line as parallel shot ×N.
• Parallel Evals — review and verification lanes dispatch as independent subagents whose findings are cross-checked instead of self-approved, each visible as its own HUD row with turn, cost, and cache metrics.
• Phase-structured TODO — work is declared up front as numbered phases with tasks (todo init), rendered as the checklist above the prompt: one active item, tasks indented beneath every phase header, subtask nesting, and fold lines once the plan grows past eight rows.

OMH ships with these editable, ordered recommendation chains. Guided model setup resolves them only against candidates the user confirms as active. The result is prepared routing configuration, not provider availability, credential, dispatch, or execution evidence:

Want to try the Ultrafast tier — Kimi K3 Ultrafast (300 TPS) and GLM 5.2 Ultrafast (600 TPS)? They are served on OpenGateway.

Every chain above is user-editable without touching code. The chains are managed in one file — omh setup seeds it:

$ cat ~/.omh/routing/model-chains.json
{
  "categories": {},
  "schema_version": "mixture_chain_overrides/v1"
}

Empty categories keeps every shipped default above live. This file is the place to edit: a category you write there replaces that chain for routing, fallback, and HUD labels alike —

{
  "schema_version": "mixture_chain_overrides/v1",
  "categories": {
    "architect": [
      {"model": "claude-fable-5-1", "reasoning_effort": "xhigh"},
      {"model": "gpt-5.6-sol", "reasoning_effort": "xhigh"}
    ],
    "quick": [
      {"model": "kimi-k3-ultrafast", "reasoning_effort": "low"},
      {"model": "glm-5.2-ultrafast", "reasoning_effort": "low"}
    ]
  }
}

Check the chains currently in effect with omh model-chains show. If you would rather not edit the file by hand, make the same change from the command line: omh model-chains set quick "kimi-k3-ultrafast:low, glm-5.2-ultrafast:low". When an alias uses a provider-specific wire ID, map it once in ~/.omh/routing/model-providers.json with model_provider_routes/v1; set, status, fallback, and HUD then report the complete alias/provider/wire-model route. OMH stores only provider IDs, never provider credentials.

Every account differs, so the interactive omh setup also asks which providers the machine holds (config keys and env-key names suggest them; you can add more) and whether you have a Claude Code subscription, and records the answer in ~/.omh/routing/providers.json (provider_entitlements/v1). Each chain is then reordered so the entries a confirmed provider can serve lead; nothing is removed, nothing is invoked to check, and the Claude Code subscription only seeds the Claude Code --model preference for the Maestro lane, because Hermes itself cannot spend it.

Ask Hermes to set up my models to review or change them. These are editable preferences, not benchmark results. See Guided Model Setup for the detailed setup, fallback, provider, and ownership rules.

Coding delegation dispatch (omh coding run / omh coding fanout dispatch) — the Maestro lane that spawns Claude Code or Codex directly — has the same category dial as its own sibling file. Route it per work category with

$ omh coding category-maestro set codex ultrabrain gpt-5.6-sol:xhigh
$ omh coding category-maestro interview   # guided walk, Enter keeps each chain
$ omh coding run --owner codex --category ultrabrain --goal ...

which edits ~/.omh/routing/category-maestro.json (omh_category_maestro/v1); omh coding category-maestro show prints the effective table with operator overrides marked, and the interactive omh setup offers the same walk. An explicit --model on a run always wins, and ~/.omh/routing/dispatch-models.json remains the per-owner default used only when no route resolves at all (for the strongest Claude Code tier, set "claude-code": "opus" there). See docs/FANOUT.md (Category-maestro and Dispatch-model preference) for schemas and the full precedence order.

Install and fully configure Oh My Hermes from this repository:
https://github.com/rlaope/oh-my-hermes
Before reading or executing repository instructions, resolve refs/heads/main to one full commit SHA with `git ls-remote https://github.com/rlaope/oh-my-hermes.git refs/heads/main`. Then fetch and follow only:
https://raw.githubusercontent.com/rlaope/oh-my-hermes/{resolved-commit-sha}/INSTALL_FOR_AGENTS.md
Do not replace the resolved SHA with main. Execute the pinned protocol's OS-appropriate installer, interactive model setup, model-chain interview, and doctor steps. Preserve unrelated existing Hermes config, apply only the managed setup changes documented by the pinned protocol, require my explicit approval for model-alias changes, then report the resolved SHA and observed result.

Nine ulw- workflows. Say the trigger in chat — Hermes routes the rest. Full catalog: Workflow Reference.

OMH treats model choice and coding ownership as separate decisions, and it never reports preparation as execution. Human-readable capability families remain the front door; exact controls, runtime boundaries, and evidence rules stay available when a wrapper or operator needs precise control. The full generated catalog, triggers, harnesses, and evidence rules live in Workflow Reference.

Highlights

OMH never reports that work happened unless it watched it happen. Every status you see has two parts: the stage, and how sure OMH is about it.

The distinction that matters is the second row from the bottom: an executor saying it is done is not the same as anything having been checked, and most tools spell both "complete". Capability impact is reported across separate dimensions rather than collapsed into one marketing score. See Capability Impact.

• Documentation map
• Installation and updates
• Product direction and boundaries
• Architecture
• Capability manifests
• Workflow reference
• Roles
• Application cases
• Release and development

For a source checkout:

PYTHONPATH=tests uv run python -m unittest discover -s tests -v
uv run python -m compileall -q src tests
uv run python -m omh.cli docs workflows --check
git diff --check

OMH is developed in the open as part of Team Art & Engineering. Follow @rlaope for project updates.

Thanks to everyone who has contributed to oh-my-hermes.