oh-my-hermes vs unlazy
The two are close in size: 3.1k stars for oh-my-hermes, 3.8k for unlazy. Over the days we have tracked them oh-my-hermes moved +233.3% and unlazy +220.4%, so oh-my-hermes is growing faster right now.
oh-my-hermes leads on model freedom. unlazy does not take any axis by a clear margin.
Stars and commit dates come from our own daily tracking. The six axes are read off each project's documentation by our review pipeline, so they describe what a project says about itself, not what we measured in its code.
Where they stand today
Provides a local-first operating layer for Hermes that enforces explicit evidence boundaries and verification gates while keeping executors and provider access observable.
- Stars
- 3.1k
- Tracked growth
- +233.3%
- Maturity
- ●●●●●
- Last commit
- 1h ago
- Language
- Python
- License
- MIT
- Cost to run
- Your API key, per-use
Implements the Depth Tree decomposition with a strict, evidence-backed runnable gate ledger that enforces approvals and re-verification for substantial agent tasks.
- Stars
- 3.8k
- Tracked growth
- +220.4%
- Maturity
- ●●●●●
- Last commit
- 29d ago
- Language
- JavaScript
- License
- MIT
- Cost to run
- Free to run locally; external agent API costs may apply
Six axes, head to head
Each axis runs 0 to 5. The label under a score is what that project's own docs claim, not a category average.
| Axis | oh-my-hermes | unlazy |
|---|---|---|
Context depth How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository. | ●●●●● Diff + related files | ●●●●● Diff + related files |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● Evidence gates | ●●●●● Approval & strict checks |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Configurable workflows | ●●●●● Config files & templates |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Self-hostable | ●●●●● Self-hostable |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● Bring your own key | ●●●●● Specific agents |
Setup ease What it takes to get a first useful run out of it. | ●●●●● One-command setup | ●●●●● One-command install |
Which one to pick
Pick oh-my-hermes if…
Local-first control plane — pick OMH when you want an installable, evidence-first workflow catalog and gating layer for Hermes that keeps execution ownership explicit and configurable.
- Model freedom: Bring your own key (5/5 against 3/5)
Pick unlazy if…
Reproducible verification — use when you need strict, executable acceptance gates, recorded approvals, and re-verification for long-horizon agent work.
What people want from each one
rlaope/oh-my-hermes
Leonxlnx/unlazy
Questions people ask
Is oh-my-hermes better than unlazy?
oh-my-hermes leads on model freedom. unlazy does not take any axis by a clear margin. oh-my-hermes is worth picking when local-first control plane — pick OMH when you want an installable, evidence-first workflow catalog and gating layer for Hermes that keeps execution ownership explicit and configurable.
Which of oh-my-hermes and unlazy keeps my code private?
oh-my-hermes: Self-hostable (4/5). unlazy: Self-hostable (4/5).
What does each one cost to run?
oh-my-hermes: Your API key, per-use. unlazy: Free to run locally; external agent API costs may apply.
Full profiles: rlaope/oh-my-hermes and Leonxlnx/unlazy. Everything else in Workflow & graph engines.