rlaope

oh-my-hermes: Add Governed Workflows to Hermes Agent

oh-my-hermes adds model routing, coding workflows, verification gates, and reviewed long-term project memory to Hermes Agent. It suits developers who want structured, observable agent work without replacing Hermes or silently treating a reported result as verified.

View on GitHub Compare
Stars
3.1k
Forks
240
Stars, last 30 days
+1,992

Our take

Health score

73/100

How it is scored
Activity
78
Community
58
Issues
73
Pull requests
83

+1,992 stars in the last 30 days

  • Merges more pull requests than 94% of the projects we track

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

5,190

Forks

412

Change since Nov 5, 2026: +69 stars·0 forks

Overview

oh-my-hermes is an operating layer and plugin for Hermes Agent. It routes delegated work by task category, provides workflows for planning, coding, research, and operations, and distinguishes work an executor reports as complete from work that has passed a verification gate.

It is aimed at developers and teams who already use Hermes and want more control over how agent tasks are divided, routed, tracked, and remembered. It does not replace Hermes or conceal a separate coding executor behind the interface; handoffs to tools such as Codex or Claude Code are explicit.

Key Features

  • Routes delegated tasks through editable model and reasoning-effort chains for work categories.
  • Provides workflows for interviewing, research, planning, parallel implementation, QA, performance work, and iterative delivery.
  • Splits accepted plans into parallel units with separate worktrees and non-overlapping file ownership.
  • Tracks execution and verification states separately, so a reported completion is not presented as a verified result.
  • Adds a terminal HUD with workflow phases and delegated-lane status, including model and cost information when available.
  • Supports explicit handoffs to Claude Code or Codex, with resumable sessions and no automatic merging.
  • Provides file-backed project memory with reviewer-approved entries, provenance, retention, and budgeted recall.

Use Cases

  • A Hermes user wants to route quick edits and complex design work to different model configurations.
  • A developer wants to implement a reviewed plan in parallel while limiting concurrent changes to shared files.
  • A team wants visible evidence of whether an agent task was merely reported complete or actually checked by tests or another gate.
  • A developer wants Hermes to retain reviewed project decisions across sessions without modifying Hermes' own memory store.
  • An operator wants to hand a named coding task to Codex or Claude Code and track that delegated session from the Hermes workflow.

Getting Started

On macOS or Linux, install and then run setup:

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

See the README and installation guide for other installation options and configuration details.

Alternatives

  • compound-engineering-plugin: It packages planning, implementation, review, and learning skills for several agent hosts, rather than adding routing and reviewed project memory to Hermes Agent.
  • agent-skills: It provides portable workflows for consistent planning, testing, and release practices, rather than integrating model routing and project memory into Hermes Agent.
  • agent-skills: It offers reusable specification, implementation, review, and sprint skills, rather than a Hermes-focused system with model routing and reviewed memory.
ProjectLanguageLicenseStarsStatus
oh-my-hermesPythonMIT3.1kNot checked yet
compound-engineering-pluginTypeScriptMIT25.4kActive
agent-skillsJavaScriptMIT109kActive
agent-skillsShellMIT2Active

Considerations

  • This is an extension for Hermes Agent, so it is most useful if Hermes is already part of your workflow; the README describes the setup and provider configuration involved.
  • Model routing preferences do not establish that a provider is available, credentials are valid, or a task will execute successfully. Provider setup and actual run evidence remain separate.
  • The project describes many workflows and integrations, so users should review its installation, model-routing, and evidence-boundary documentation before relying on a particular workflow.
  • The README says no measured Hermes-versus-OMH product comparison has been published yet. Its stated coding-task measurements should not be treated as a published overall product benchmark.

Found this useful?

Share it with someone who would like oh-my-hermes.

Comparisons