Chisle
The coding-agent plugin that bills 52% of a bare model across 20 live tasks. Terse persona + tool-output compressor + context diet.
翻訳待ち
All in one plugin for Hermes Agent ⚚ the coding intelligence, a long-term memory system and model optimized workflow packages
翻訳待ち
Loading the full README. The saved excerpt is shown below.
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.Read the full README ↗Your Hermes bots and coding agents, in one window.
macOS (Apple silicon) · macOS (Intel) · Windows · All releases →
The ultrawork agent with AI coworkers wired into you. Just type dag-ulw.
English | 简体中文 | 日本語 | Русский | 한국어 | Español | Français | Deutsch | Português (Brasil) | Italiano
oh-my-hermes is an operating layer for Hermes Agent. You keep talking to Hermes. OMH puts a coworker with its own skill and model on each lane, in parallel. It never patches or replaces Hermes, and it never reports planned work as done.
curl -fsSL https://omher.app/install | sh
omh setup
The right model for every lane.
Each lane is tagged with a work category: ultrabrain, deep, visual-engineering, quick and more.
The category picks that lane's model chain and reasoning effort, and you can edit every chain.
When a provider rejects a model, the chain moves to the next one instead of silently downgrading.
omh model opens the picker; see which model runs each lane.
/dag-ulw graph runs.
Your goal becomes a graph of small nodes, and the ready ones run in parallel.
Each node runs on its category's model and effort; nodes running at once never share a write scope.
A separate node checks the goal, and failed nodes are repaired before the report.
Expert skills on demand.
A hundred-plus omh-* specialists: frontend, backend, Rust, security review, verification gates.
You never call them; the router loads the right ones into the run as tool calls.
LSP in the loop.
Definitions, references and renames come from the language server, not text search.
Aliases, re-exports and shadowed names are renamed by meaning, not by matching text.
Off by default; enable lsp_tools in the OMH plugin settings.
Long-term memory you can trust. Nothing is remembered silently: each candidate is kept, refused or deferred with a written reason. The next session gets a recall pack ranked for its task and cut to a token budget. Hermes' own memory is never read or patched.
OMH Native.
Bare omh opens OMH's own TUI on Hermes' gateway; switch its launch look with /theme.
/dag-ulw prints the box graph, then a live lane tree with each lane's model, effort and tokens.
Steer or interrupt an agent from the agent list, run a ! shell line, and rewind with Esc Esc.
Evidence before "done".
Every status names its stage and how sure OMH is about it.
Plan · not run · Code · reported done · Test · verified
A run counts as verified only when a test, review or CI gate actually passed.
Just type /dag-ulw, and you're a graph engineering master.
Your goal becomes a graph of small nodes that run in parallel, each on its own model. A separate node verifies the goal before you get the report.
Built on
This is the beginning of the README. Read the rest at the original. Read the full README ↗