Zeus brings three major changes to OMH: a dedicated terminal, long-term memory you can maintain through conversation, and specialist workflows connected to Hermes’ native capabilities.
Work with Hermes through OMH’s own terminal interface. Follow tool calls, inspect diffs, check subagents, and steer a running task without leaving the conversation. Session pickers, history search, rewind, and clearer approval and question controls make longer sessions easier to navigate.
Search, confirm, correct, and retire memories by talking to your agent. When Hermes’ built-in memory fills up, OMH can preserve approved copies in its long-term store before freeing native memory space.
Retrieval prioritizes relevant context and current values. Memory support extends across TUI, Desktop, and supported messenger conversations, with user, channel, project, and profile boundaries governing what can be recalled.
Bring domain-specific methods into research, planning, coding, design, and everyday work without maintaining a second set of controls.
OMH workflows now use more of Hermes’ native capabilities: one plan checklist, source registration and citation checks, structured review results, Automation Blueprints, and recorded outputs from document and image tools.
Restart or reload Hermes after updating. Launch with omh.
The OMH terminal falls back to Hermes’ own interface on unsupported environments, including Windows. Updates release OMH-owned styling from the stock Hermes interface while preserving user-owned customizations.
The complete version-bound changelog follows below.
-
Indonesian ships as a trigger language pack. src/routing/trigger_packs/id.json,
contributed by @fauzibrevy-hub (#2154), covers the 21 skills the ja and
zh packs cover, with phrases such as tinjau kode, audit aksesibilitas,
build gagal and lakukan riset mendalam. It is the first pack in a
Latin-script language, and that shares the English token space: Indonesian
borrows bug, crash, error and file. So a shipped pack phrase written
entirely in ASCII now scores only as a whole phrase. Its words never join the
skill's trigger tokens, and the lexical shortlist leaves it out of the
skill's English document and anchors. Tests hold every skill's trigger
tokens, lexical document and anchors equal to the view with its ASCII pack
phrases taken out, and refuse an ASCII hold-back entry that none of the
pack's own non-ASCII phrases carries. ASCII pack phrases merge after the
ja, ko and zh ones, so SKILL.md descriptions and capability rows,
which show only a skill's first triggers, keep the cues they showed before.
Phrases that routed ordinary Indonesian chat (a team work plan, "ask me one
at a time", a medicine reminder) did not ship, and neither did a few that
read as word-for-word translations. ultrawork carries one Indonesian
phrase, implementasi paralel: its always-loaded body had room for one
under the byte ceiling. id is an input language only: it is not a
--language / OMH_LANG output choice.
-
OMH TUI tool calls read as in Claude Code. Each call is one row,
⏺ read_file(README.md) 0.2s: a ⏺ in the accent while it runs, green
once done, red when it failed or was denied, in place of the ✓ and ✗
marks, then the tool's name and what it ran on in parentheses. What it
printed, and an edit's diff, hang under ⎿ , as a command's output
does. A read or a load no longer echoes the first lines it read: it says
Read 715 lines (read_file), loaded skill omh-docs (skill_view) or
12 matches (search_files). A resumed session's earlier calls read the
same way, with a dim ⏺ (Hermes' record keeps no outcome) and an edit's
diff under it, in place of the · read_file README.md rows with a blank
row between each.
-
An answer you gave Hermes reads under the call it was about. The
record of an approval or a question (✓ allowed once · <command>,
✓ blue · Which colour?) was written above the turn's live tool calls, so
with one row per call it stood over the first read of the turn. It is now
the first row under the call that asked, ⎿ ✓ allowed once · <command>,
on the same green or red band; a denial reads ⏺ terminal(…), then
⎿ ✗ denied · …, then Hermes' denial line. With no call running (a
subagent's question after its turn), it is still a row of its own. A
clarify question Hermes timed out, or one you cancelled, says so once under
its call (⎿ ✗ timed out · Which colour?), not again in a bare
⎿ timed out row under that.
-
An OMH TUI diff no longer doubles each changed line. Hermes pads every
added and removed line of an edit's diff with spaces, to 143 columns in a
live patch, so on any narrower terminal each green or red band wrapped into
a second, empty band row. A diff line's trailing spaces are dropped now;
the band still reaches the right edge.
-
The OMH TUI's working row reads as Claude Code's. It was a braille
spinner and Hermes' kaomoji text (⠋ (⌐■_■) analyzing... (12s)). It is now
✶ Analyzing… (12s · ↓1.2k tokens · thinking with high effort · esc to interrupt): a glyph turning through · ✢ ✳ ✶ ✻ ✽ (still under reduced
motion), Hermes' verb without its face or dots (Working… when it gives
none; a stall or retry notice, No response from provider in 120s — reconnecting…, keeps its words), and the effort when the session reports
one. A tip naming a key sits
under it, one a turn, on a terminal 16 rows tall or more
(⎿ Tip: ctrl+o shows the whole transcript); it is local text and nothing
is sent. interrupting… lines up under the same glyph column.
-
Your prompt and a turn's end read as in Claude Code. A prompt in the
OMH TUI transcript is a dim > and dim text, with no tinted band behind
it, and a command's echo takes the same > (> /model). The ↳ you: …
reminder over a running turn loses its band too: ↳ you: in the accent,
your words dim. A turn's done
line is one dim line under the reply, ✻ 5s · 3 tools · ↓1.3k, without
the rule that ran to the right edge.
-
The OMH TUI's composer is a rounded box over one dim info line, as in
Claude Code. The composer's two rules, the mode row and the dark status
band are gone. The composer sits in a box (╭─╮, │ > … │, ╰─╯) that
keeps its colour in every mode, and the line under it, two cells in under
the box's text, says the mode or the keys that matter now on the left (? for shortcuts
while the composer is empty, ⏵⏵ accept all on (⇧⇥ to cycle) in accept's colour, ⏸ plan mode on (⇧⇥ to cycle) in plan's, a
question's or a picker's keys) and the model, ctx 5% and effort medium
on the right, with the OMH HUD's repeat and in-flight tool counts first
when there are any. The ⚚ OMH brand and the idle / running words
are gone: the working row, the strip and the queue rows already say them,
and during a turn the left names only the steer keys, since the working
row already offers esc to interrupt.
On a narrow terminal the right side gives way first, the model shortening
to deepseek-v4.1-flash and then v4.1-flash before it goes. The line is
on every terminal of 3 rows or more, so the mode is never hidden, and the
agent list now opens from 6 rows (and 20 columns) instead of 10. A ! shell line keeps its ! shell
label, and its > mark turns the accent colour.
-
The OMH TUI opens on a clean screen. As it starts, what your terminal
showed above the cursor (your shell, the warnings hermes printed) scrolls
up into the terminal's own scrollback, and the TUI starts on the top row.
Nothing is erased: scroll up to read it, until a full redraw (a resize,
Ctrl+L, /redraw) clears the scrollback. A launch that falls back to
Hermes' own terminal leaves the screen as it was.
-
Hermes' note about a skill named like a built-in command is no longer an
OMH TUI notice at every start. Hermes' own bundled plan skill shares
its name with /plan, so every start said Hermes' command catalog: slash command /plan unavailable — name taken by built-in; use /skill plan.
/help now lists those notes, in Hermes' words, under the skill count; a
real discovery failure (skills, quick commands, plugins) is still a notice.
-
omh handoff-risk-scan --repo completes on ordinary repositories.
The scan charged the raw bytes of every Git listing to its 1 MiB metadata
budget, and the index listing with its stat lines alone prints about 190
bytes per short-path entry, so a clean repository of 4,500 short-path
files, or 6,538 files with 59-byte paths, ended in
scan_error / metadata_oversized, far under the documented 10000 entries
(#2157, reported by @jhlee0409). The budget now charges what the scan keeps:
the HEAD and branch output, each committed path with its mode and object id,
each index path the commit lacks, and the untracked listing; a path in both
the commit and the index is kept and counted once. The 10000-entry and
1 MiB limits are unchanged. The tree and index listings are read in 64 KiB
pieces up to a fixed cap derived from them, and a longer listing still kills
the Git process and ends the scan with metadata_oversized. Git output the
scanner failed to read is a scan error, never an empty listing.
-
A party named before a Korean data-share place, or after an English one,
keeps the review. Korean puts the data, and any party, before the place,
and only the place was read: "보험사가 원하는 고객 엑셀 개인정보 마스킹해서
개발팀에 보내줘" read inside and named no review. Every word outside the
places and before the requested verb must now be a closed word, as English
already reads the span before a send: data containers and field names in
either script, a verb the rule knows, an inside place word, a determiner or
a softener, and a word that says whose records the data holds (고객, 회원,
환자, ...) only bare and right before a data word. A party acting
("보험사가 원하는"), owning ("보험사의", "고객의"), a purpose ("협력사용",
"보험사를 위한") or any other noun ("삼성 고객 파일") keeps the review, and
"-기 전에" is a step rather than a place. Korean also read only the first
sentence; a later one now counts when it sends, names a recipient or a
place outside, or names a party acting ("... 개발팀에 보내줘. 벤더한테도
보내줘.", "... 보험사가 볼 거야."), and remarks alone ("급해요.") say
nothing. In English a place now ends with its sentence (".", "!", "?" or
";" before a space), so "... send it to the dev team. It's urgent." names
no review, while every sentence is still read for sends and the words after
a place must be remarks -- thanks, please, urgency -- so "... to the dev
team. Acme will review it." and "... Also cc Acme." keep it. A line break
alone ends no sentence, because the router reads it as a space; a period
before a space ends one even after an abbreviation ("Acme Inc. today", "the
U.S. team"), which only cuts a place short. Between a send and its "to"
only closed words may stand, read as the span before the first send is:
the data, also as protected, counted or the version the redaction made
("the anonymized copy", "both files", "the updated file", "the customer
export"), the verb's particle, "straight" or "directly", and remarks; so
"send it where Acme wants it, to the dev team" and "send the Acme copy to
the dev team" keep the review, and so does any other word there ("send the
sorted export to the dev team"), the safe direction. The Korean reader no longer
opens a quote at an apostrophe after a Latin letter or digit, nor closes
one before a Latin letter, so the router and the hint read "고객 정보
마스킹해서 Acme's team에 보내줘. It's urgent." alike; a quote a Korean
particle follows ("'고객 정보'를") is still a quote.
Measured against main on sets written before the change (104 Korean
outside rows, NFD copies included; 80 Korean inside controls; 57 English
sentence-end rows) and every earlier data-share set: no request to an
outside party lost the review on admission, router offers or the hint, and
the router and the hint never disagree with every cache cleared (three
disagreements on main). Korean outside rows gained the review on
admission and the hint from 16 to 98 of 104, and on router offers from 2
to 26; the six left are two that name a regulator, which reads as a legal
question, and one that names no personal data, each with its NFD copy.
Korean requests sent on in a later sentence gained it from 0 to 12 of 12.
English inside requests followed by a remark stopped firing (20 to 5 of
20), and no English inside request on these sets or the review's starts
firing. Of 196 Korean inside rows that read inside on main, 8 now fire, the
safe direction: an order history, survey responses, "this month's" orders,
and "고객의" (a customer's), each with its NFD copy. On the review's own
sets no outside request lost the review either, and 19 more Korean inside
rows now fire for the same kinds of word: time words ("이번 달", "지난달",
"어제 받은", "오늘 안에"), descriptors ("주문 내역", "거래 내역", "설문 응답",
"가입 정보"), an inside team acting ("우리 팀이 만든", "개발팀이 요청한"), and
"고객의".
-
A plural possessive no longer hides the rest of a message from routing.
The routing masker read the ' of "the customers' export" as an opening
quote. Nothing closed it, so everything after it was masked and no matcher
read the verb or the place: "Redact the PII in the customers' export and
send it to Acme." got no data share review from the router or the hint, and
in "explain the users' '$ulw-work' snippet" the possessive paired with the
next quote and left $ulw-work to dispatch. A ' that ends a word now
opens no quote: one right after a letter or digit that is not East-Asian
wide (CJK, kana, Hangul or fullwidth), and right before whitespace, one of
.,;:!?)], an East-Asian wide character or the end of the message. It
still closes one that is open. A ' after a space or an East-Asian wide
character (고객' list), or glued to more text (f'$x', API''), still
opens one.
The data share review also reads ’ between two letters ("it’s", as Mac
and iOS type it) as an apostrophe, as it reads ', not as a quote.
-
Two OMH TUI subagents whose goals start alike read differently on the
strip. The strip names an agent by the first words of its goal, and two
goals that began the same were numbered with those words, so two shell
tasks read 1·Run the shell 2·Run the shell and nothing said which was
which. Agents that share a name now show the word where each goal parts
from the one nearest it, out of any quotes or backticks around it (with the
next word when it is one like in), so goals that part at `echo alpha`
and `echo beta` read …alpha and …beta; the numbers stay only for
goals whose words still read the same.
-
A fresh OMH TUI session no longer shows the last session's subagents.
Hermes writes a session's state.db row on its first prompt, so a new
session's key mapped to nothing until then, and the HUD reader fell back to
every conversation's recent delegate children: a session nobody had typed
in yet opened with [Agents] │ [global] 2 done and the previous session's
rows. The TUI's own key now owns no children until its row exists, and the
panel stays empty. Other readers that name an unmapped reference (the
desktop pane, the plugin tools) keep the documented global fallback.
-
Denying an OMH TUI approval also stops the turn, as Esc does in Claude
Code. A deny went to Hermes and the turn went on, so the model often
tried the next thing straight away. Every deny the person gives (Esc,
Ctrl+C, d, n, Enter on deny, and Up then Enter typed ahead) now sends
the explicit deny first, so the waiting tool ends denied, and then
interrupts the running turn (session.interrupt, the call Esc makes on an
empty composer); with no turn running only the deny goes, and the mode row
then says d or esc denies. An approval a
subagent asked for stops the session's whole turn. The tell row is the one
deny that does not stop: it redirects the running turn instead. The mode
row says so in plain words, ↑↓ pick · enter confirms · d or esc denies and stops, down to esc denies and stops on a narrow row.
-
An OMH TUI approval can be denied with what to do instead. Telling
Hermes what to do after a deny took a deny, then a separate Ctrl+Enter
steer. The approval's last row, no, and tell Hermes what to do instead
(last, as Claude Code puts its "No, and tell Claude" row), sends the
explicit deny at once, so the turn is not held, and opens the composer
labelled ↪ tell Hermes what to do instead · enter sends · esc cancels.
What you send goes into the running turn as a steer through the same path
as Ctrl+Enter (a refused steer waits in the queue, an unanswered one comes
back after 120 s), or as an ordinary prompt once the turn has ended, which
waits behind a prompt you queued and never steers it; the tell row of a
later approval keeps that composer open with what you typed. Esc sends
nothing more and brings your draft back. Deny stays first and
highlighted, the highlight still stops at both ends, and no digit or
letter but d and n answers.
-
An OMH TUI approval offers Hermes' "always allow" when Hermes does.
The OMH TUI left Hermes' always choice to hermes --tui. When Hermes
lists it (it leaves it out where a permanent allow is refused, such as a
command its smart approval flagged), the approval now has a fourth row
under allow this session, labelled with what it allows, always allow recursive delete (Hermes saves it): Hermes saves that kind of command in
its config (command_allowlist), so later ones run without asking. Like
every allow it takes the arrows and Enter; the transcript records
✓ always allow sent (Hermes saves it) · <command>.
-
Every OMH TUI question asks for your attention, not only an approval.
An approval rang the bell; a clarify question, a sudo password or a secret
signalled nothing, and Hermes drops a clarify question nobody answers after
300 s by default. Each request now rings the bell once as it opens and,
on a terminal that shows them, sends the notification a long turn's end
sends (OSC 9 in iTerm2, WezTerm and Ghostty, OSC 777 in foot and rxvt),
saying what Hermes asks (Hermes asks: Which colour?, never a value).
OMH_TUI_BELL=0 keeps all of it quiet.
-
The OMH TUI stops billing your answer time to Hermes. While an
approval or a clarify question was open the working row kept spinning,
⠼ working… (16s · ↓262 tokens), beside the status line's waiting on you; a command you took 20 s to allow then read ✗ terminal rm -rf ./tmp-a 21.8s, as if it were slow. The working row now reads ? waiting on you (11s) with no spinner and one clock, that wait's (the OMH tool
count beside the model shows no seconds of its own meanwhile, and leaves with the
turn instead of lingering into idle); a tool's row
leaves the wait out of its time; and the done line keeps the turn's wall
clock with the wait beside it, ✻ 30s (27s waiting on you) · 1 tool.
-
The OMH TUI's transcript records how each question ended. A clarify
question left only Hermes' tool row (✓ clarify Which colour should I use? 2.5s), a ✓ even when it was cancelled, and the answer appeared
nowhere but in the model's reply; a sudo or secret prompt left nothing.
Like an approval's ✓ allowed once / ✗ denied, the answer now goes
above the call it was about: ✓ red · Which colour? (ticked labels
joined, or what was typed, as Hermes reads the answer: without the
(Recommended) tag it shows on a choice, and with empty items of a
multi-select answer left out), ✗ cancelled · <question> or ✗ skipped
(also a multi-select answer with no item left), and
for sudo or a secret only ✓ answered or ✗ declined, never the value. A
question Hermes withdrew reads ✗ timed out, ✗ interrupted or
✗ withdrawn (<reason>) with what it asked, in place of the amber
Hermes withdrew its <method> request (<reason>). A clarify call that got
no answer is a red ✗ clarify row with cancelled, timed out or not delivered under it, not a ✓.
-
OMH TUI clarify questions that take several choices are answered with
several. Hermes' multi_select was never read: the question looked like
any other and went back as one label, and an answer typed as 1,3 reached
the model as one string. Such a question now says (choose one or more)
and boxes each choice; Space or the choice's digit ticks it, Enter sends
the ticked ones (the highlighted one alone when none is ticked), and an
answer of your own joins them. The answer is the JSON list Hermes' Ink TUI
sends (["ham","cheese"], in the order ticked), in the same answers
frame as before; a single-select question is unchanged.
-
An OMH TUI question says when others wait behind it. A second request
that arrived while one was open queued with nothing on screen to say so;
the open question now ends its first words with · 1 more question waiting (or the count). A request the TUI cannot show (a terminal read, a
vault prompt) that arrived behind an open question waited for it to close
before its decline was sent; it is declined at once, with its notice, as it
is when nothing is open.
-
OMH TUI clarify choices wrap instead of being cut to one row. At 80
columns ❯ 1. Blue/green with a full traffic switch after smoke tests pass on the gree… lost the (Recommended) tag Hermes puts at the end of the
first choice, and the rest of a choice up to Hermes' 8000 characters. Each
choice (an approval's too) now wraps under its number, the slot counts
rows rather than choices, and a terminal too short for every choice keeps
the highlighted one whole, or its first rows, with … ctrl+o shows all.
Choices it cannot list are marked beside the list on the side they are cut
(… +3 more choices, 1 ticked · ctrl+o shows all; an approval's
… more choices, which numbers nothing), so a cut tell row or a ticked
choice scrolled away is never silent, and the marker no longer ends the
question's text.
-
An OMH TUI question you cannot see whole says so, and Ctrl+O shows it.
A long approval command showed its first 6 of 20 lines at 24 rows, and
Ctrl+O did nothing while the approval was open; below 10 rows a cut had no
marker, at 6 rows no command row was drawn at all, a narrow terminal cut the
approval's header, and under 6 rows or 20 columns a sudo, secret or typed
clarify question showed no label. Every cut now ends with … ctrl+o shows all (… +14 more lines · ctrl+o shows all under a command's first lines),
from 6 rows a command's first row is drawn, the header and a value prompt's
label wrap, a tiny terminal keeps one row for a typed question's label, and
Ctrl+O while a question is open pages it whole: it answers nothing, and q
or Esc returns to the question with the same row highlighted.
-
Enter on an OMH TUI / or @ menu takes the highlighted row, as in
Claude Code. A command typed in full still runs on the first Enter. Esc
closes the / menu, and both menus stop at their ends.
-
The OMH TUI's Ctrl+R search and agent list stand where the composer
was, as the pickers do: the composer is hidden, the search's caret is at
the end of its query, the agent list takes every key (only its own act, so
typing never turns into a steer; Esc, Left, q or Ctrl+C leaves it), and
the mode row says their keys.
-
An interrupted OMH TUI turn says so until Hermes stops, and the queue
waits. After Esc or Ctrl+C the working row says interrupting… until the
turn ends, and the queue does not start: queued prompts come back into the
composer unsent, a queued ! line waits until your next prompt.
-
The OMH TUI's /model picker opens on the session's model. It marks
that model (first, when no provider lists it) and shows Model (12/162)
once it scrolls.
-
OMH TUI list commands leave no echo in scrollback. Bare /sessions,
/rewind, /keys, /history, /logs and /redraw leave no > /name
row.
-
New OMH TUI keys. Ctrl+X opens the session picker, Ctrl+_ and Ctrl+Y
undo and redo in the composer, and Ctrl+Z suspends to the shell on POSIX
(Hermes' gateway stops with it; fg draws it again under what the shell
printed). Where Shift+Enter would send, the mode row names the
newline keys while a draft spans lines.
-
/omh-model no longer stops the OMH TUI's gateway. A reply keeps
streaming underneath and a question closes the picker with nothing saved;
the picker stops at its ends and says esc cancel.
-
A crashed Hermes gateway comes back. When Hermes' tui_gateway exits
with a failure, the OMH TUI starts it again from the launcher's
environment and resumes the session, saying so (The Hermes gateway exited (code 1): starting it again and resuming session <id> (1 of 3 in 60 s); what you type waits until it is back, and ctrl+c leaves.), at most three
times a minute.
Each attempt waits up to 15 s for the new gateway (HERMES_TUI_STARTUP_TIMEOUT_MS
when set, as in Hermes' own TUI), Ctrl+C or Ctrl+D while it waits leaves
with the new gateway stopped, and one that exits before it resumed the
session uses an attempt, as in Hermes' own TUI. An
open question closes unanswered, a running turn is reported lost and not
sent again, a steer the old gateway had not answered, and what was typed
in an approval's tell field, come back to the composer at once, the
subagents on the strip stay there (those still
running marked interrupted) rather than reappearing as look-alike rows in
the HUD's [Agents] block, and what you queued comes back as after an
interrupt.
AGENTS.md and CONTEXT.md now say the frontend spawns one child at a time
and respawns it so.
-
The OMH TUI's composer sits right under the output until the screen
fills, then stays on the bottom rows. A fresh session showed the banner,
then 20 blank rows (110x34) to 36 (200x50), then the composer, and 6 to 12
blank rows stayed above it after a short turn, during an approval and after
a resize: the live region was padded to the screen's height at every start
and redraw and never got shorter. It is now drawn right under the last line
printed (one blank row under a turn, the spacer every block opens with) and
follows the content until its last row is the screen's last row; from then
on it keeps its height, so a list or question closing above the composer
leaves blank rows above it, filled by the next output, and does not pull it
up. A resize or a redraw starts again under the output. Short of the bottom
rows the / and @ menus open under the composer where they fit, as in
Claude Code, so typing / no longer moves the composer down by the menu's
height and Esc back up; on the bottom rows they open above it, and output
that brings the composer there while one is open takes it above with that
output, so closing it moves nothing. The startup query
that asks for the background colour also asks for the cursor's row (CSI
6n, inside the same 0.1 s wait), so a start from the last row of a
terminal already holding output is on the bottom rows from its first frame;
only a terminal that does not answer that cursor-position query follows the
content until the TUI's own output has filled the screen once.
Lines that leave the top of the streaming tail are written over the rows
they were drawn on, so the rows under them are not painted again, and while
the screen is not yet full a new tail line is inserted where it goes (IL),
so the composer and the rows under it move down without being painted again
(a reply streaming onto an empty 40-row screen writes 232 bytes a frame,
where following the content had doubled it to 605).
-
Each tool call is its own row, and a cut output names the key that shows
the rest. A turn's calls were folded under one ⏺ Tool calls (2) header;
each call is now a row of its own (its mark, name and what it ran on) with
what it printed under it, as in Claude Code, and the parallel ×K badge
that header carried is gone with it. A tool's output, a diff and a
command's output cut short end … +N lines · ctrl+o shows all (rows for a
command), where they named /history or nothing: Ctrl+O opens the details
view at its end.
-
A finished plan leaves the OMH TUI's panel. The plan stayed above the
composer into later, unrelated turns. Once every item is done it now shows
✓ 3/3 until the turn ends and then goes, as Claude Code's list does, with
its final list written to the transcript above the done line under the
header the panel showed ([Plan] │ ✓ 3/3, as /todos now heads it too); one already
finished when the session opens is not drawn, and a new plan is. The
[Plan] │ 2/6 . dot was the header's walking ellipsis, caught at one dot;
it is gone, and the active item's colour wave still shows work moving.
-
The OMH TUI states the approval mode once. After Shift+Tab the mode row
said ⏵⏵ accept all on · approvals off for this session while the status
line said yolo mode: off: that chip read Hermes' saved state through the
HUD, which lags behind a switch. The status line no longer carries it; the
composer's rules and mode row (the status line on a short terminal) say the
mode, as Hermes confirmed it for the session, in the words the docs use.
The mode row also says what each mode means and what Shift+Tab turns on
next, Claude Code style: between turns ? shortcuts · ⇧⇥ accept all/plan · ctrl+t effort (medium) (it said ⇧⇥ mode · ctrl+t effort with a separate
effort medium on the right), in accept all ⏵⏵ accept all on · Hermes asks no approvals in this session (⇧⇥ plan/normal), in plan ⏸ plan mode on · prompts go as /plan (⇧⇥ normal/accept all), with shorter forms of the same
words on a narrow row. The effort is said once, as ctrl+t effort (medium),
and the keys list uses the same words for Shift+Tab and Ctrl+T. It names the
level Hermes' config sets from the start of each session, /new and
switches included (read from the settings the TUI already reads), until
Hermes names the session's own once it has built the session's agent, and
where none is configured it says ctrl+t effort (default) (the
provider's own default applies) instead of no level at all; Ctrl+T steps
from the level shown.
-
A first Ctrl+C between turns says ctrl+c again to exit on the mode row
for the 2 s a second press exits in, as Esc's first press does, instead of
leaving a Ctrl+C again to exit notice in the scrollback every time.
-
The OMH TUI shows three things Hermes sends it and it dropped: what the
background review saved to memory or skills (review.summary, a transcript
line), a standing /goal (session.control.update, one row above the
composer worded as Hermes' Ink goal bar: ⊙ goal · 3/20 turns · <title>,
parked or paused with its reason), and a mixture-of-agents turn (moa.*:
each reference model's answer as a collapsed ◇ Reference 1/3 — <model>
row, and MoA: refs 2/3 then MoA: aggregating… on the working row). The
gateway already wrote these to the TUI; showing them sends nothing.
-
The status line follows a light terminal. It kept the palette's dark
bar on a light screen (sky's #0A2229 under white). On a background the
terminal reports light (or COLORFGBG names, or /theme light) the bar is now a light tint of
the palette's own bar colour, its words still 4.5:1 and its │ dividers
3:1 against it; a dark terminal, and one that reports nothing, keep the
palette's bar.
-
The keys list names the /model picker beside the /sessions and
/rewind lists, which take the same keys (?, /keys, and INSTALLATION's
table).
-
A team inside the company is internal for data-share-review, in English
as in Korean, and only when it is proven inside. Owner decision
(2026-10-16): sending personal data to a team in the same company is
internal, so the review does not fire; it fires only when the data leaves
for an outside party (a vendor, provider, partner, contractor, third party,
or an external service). English admission read any verb that sends a file
as the file leaving, wherever it went: "redact pii in the export before we
send it to the dev team" dispatched the review. The gate fails safe: a place
is inside only when every word of it is an inside word, in closed tables
both languages read -- an anchor (a teammate, a colleague or coworker,
internal, in-house, QA, staging, a test or dev server; 사내, 내부, 동료,
스테이징), a team or department with an owner (our, my, another, or an
internal function such as data, dev, marketing, finance, hr; 우리, 다른, 개발,
재무, 인사), a determiner, or a system beside an anchor (the internal wiki,
the staging server; 사내 위키). Any other word keeps the review: a company
("the Acme team", "Acme's data team"), a client or customer ("the customer
success team", "고객지원팀"), an organisation ("the Department of Health",
"은행 담당 부서에", "다른 회사 동료에게"), a relative clause ("a former
colleague who now works at Acme"), a place after "at", "of" or "for" ("the
data team at Acme", "the dev team for review"), a team with no owner ("the
team", "팀 전체에"), and Hangul in an English place. In English, only closed
words -- where the data is, a determiner, the speaker, data containers and
personal-data field names -- may stand from the lead verb to the first
send, its object included ("the export Acme will get", "the CSV the bank
wants" and "before Acme sees it" keep the review). A word that names whose
records the data holds (customer, user, patient, client, member, employee,
staff, student, donor, applicant, subscriber, account) may stand there only
right before a data container or a field name, not possessive and not
after "for", "to" or "from": "the customer export", "the patient CSV" and
"the user logs" describe the data, while "the customer's export" and "the
export for the customer" keep the review;
every later send must name such a place after its "to" or "with", and so
must every place it joins ("the data team and Acme", "cc the auditor");
"give", "hand" and "pass" without "to" send nothing to the person and
otherwise take their first object as the place ("give Acme a copy" keeps
the review). A Korean place is read back, however many words, to a step or
a joined form of a verb the rule knows, so a noun ending in 서 or 고 is read
on ("경찰서 보안팀에" keeps the review); every place in the sentence must be
inside, and an English recipient word ("vendor team에") keeps the review.
Both surfaces mask quoted, code, link and relayed text before they call the
rule, and each passes the masker's own report that it removed something, so
no place is then proven inside ('the "Acme" data team', "the dev team
https://acme.com"). Measured against main on 160 requests written for this
change, 140 written blind by a separate agent, and the reviewer's sets
written before reading the code (mine2.tsv and its NFD copy, adv.tsv
to adv4.tsv, r3.tsv, r3b.tsv): on these sets no request to an outside
party lost the review on admission, the router or the hint, and the two
surfaces never disagree with every cache cleared. Korean outside requests
gained it (29 to 40 of 40, 32 to 34 of 35, 34 to 53 of 53, 10 to 31 of 31,
1 to 18 of 18), and 47 adversarial rows written for the compound-modifier
rule ("the customer export the regulator wants", "the patient CSV for the
insurer", "the customer's export") lost nothing. Inside requests that still
fire, the safe direction: English 2 of 36, 12 of 35 and 14 of the
reviewer's 31 (each for where the data goes: a manager, HR, the intranet,
a bare "engineering", "in Seoul"); Korean 2 of 36, 14 of 35 and 5 of 20.
The three requests the decision named without a file ("redact the pii and send it to the dev
team") were never admitted, since English admission needs a file-shaped
carrier; they are pinned as negative controls. Every table is pinned by a
literal snapshot, and a list of outside words must keep the review. Files
and folders stay inside only in Korean ("엑셀로 내보내줘").
-
Korean spend and data-share requests reach their gates. "내 카드로
결제해줘", "이거 결제해줘" and "송금해줘" fell back with score 0, "고객 정보
마스킹해서 벤더한테 보내줘" dispatched gateway-intent-card, and "개인정보 지우고
외부에 공유해줘" asked about automation-blueprint: both gates' admission rules
read only an English lead. A Korean request puts its verb last, so a new
bundle reader (korean_request) reads the request clause's last predicate,
and only when a request ending closes it ("-해줘", "-해 주세요", "-해줄래?",
"부탁해"), the way "please" marks an English one. It skips a greeting or an
address before the request ("안녕하세요.", "헤르메스,"), removes a label's
text ("버튼 라벨: ...") and quoted text, and drops what comes before a
negation it knows (말고, 않고, 마시고, 마세요, 마요, 없이): "카드로 결제하지
말고 견적만 보내줘" asks for the quote. spend-gate admits it when that
predicate spends (결제, 송금, 이체, 구매, 주문, 예매, "사줘", ..., but not "결제
처리해줘"); books, tops up, subscribes, renews or donates something one pays
for with a price, money, the person's wallet or account, or a card as the
means in its own clause ("카드로 호텔 예약해줘", not "가격 5000원으로
갱신해줘" or "제 카드 정보 갱신해 주세요"); or sends money as its object
("엄마한테 10만원 보내줘", not "결제 금액 10,000원 영수증 이메일로 보내줘").
data-share-review admits it when it protects personal data (익명화, 가명 처리,
비식별화, or masking, deleting or covering personal data) and the data
leaves: a recipient named as where it goes ("벤더한테", "외부에"; not
"업체 목록에서" or "업체별로"), or a verb that sends it to no team, file or
folder of the person's own ("스테이징에", "개발팀에", "엑셀로"). Each gate
scores only its own phrases, which an admitted request always says, with
no boost: one phrase scores below the dispatch line, so the router asks, as
it does for "please send money", and a second one (the person's card, a
recipient) dispatches the gate unless another skill outscores it. The
Korean phrases live in the bundle beside the English ones, since the rules
read them, and "예약" and "보내" are declared as shared with
automation-blueprint. Measured on seven sets of everyday-sense Korean
negatives (90, 80 and 42 of my own sets, and a reviewer's 82, 34, 75 and
27), no sentence names either gate on either surface. Recall is partial: on
a set written blind by a separate author and first measured at an earlier
version of the rule, the router offers 23 of 40 spend requests and 19 of 40
data-share requests (the hint 24 and 21). Every set has since been read
while the rule was revised, so none is held out for this version.
-
Korean diagram, LLM-wiki and token/cost requests stop going to the wrong
skill. codebase-uml's diagram check compared the composed words
"다이어그램" and "시각화" with the router's NFKD-folded tokens, so no Korean
diagram request reached it: "코드베이스 다이어그램 그려줘" asked about
codebase-onboarding while the in-session hint named codebase-uml. Both words
are folded before they are compared and read as prefixes, because Korean
attaches the particle ("다이어그램이"). On the router the English boundaries
hold in Korean too: 클라우드, 인프라, 쿠버네티스 and 서브넷, bare or with a
particle ("클라우드의"), mark an infrastructure diagram that is the bundled
architecture-diagram skill's job unless a Korean or English code word is
also there. Because the check now runs, "시각화해줘" joins the skill's
Korean whole-phrase-only tokens: the trigger "코드베이스 시각화해줘" made it a
scored token of its own, which would have named the skill for "매출 데이터
시각화해줘". "LLM 위키" and "LLM위키" now name the pattern Hermes' bundled
llm-wiki skill builds, as "llm wiki" did: the wiki blueprint withdraws,
and so does the greenfield interview, which Korean, exempt from the
weak-evidence check, dispatched on that guard alone. English llm-wiki
requests still clarify; their leading candidate moves from deep-interview
to the next scored skill. ops-observability-card loses its bare "비용" and
"토큰" triggers, which dispatched it for "토큰 저장 방식 바꿔줘" and "이 API 호출
비용 줄이는 코드 짜줘"; its Korean trigger count drops from 9 to 7. The
card's guard keeps them as telemetry words, as it keeps "token" and "cost",
but no longer reads "알려줘" as a status request, a word its English list
never had. Korean token and cost usage is read from "토큰 사용량", "토큰 사용
추이", "토큰 소모(량)", "토큰 소비(량)" and "비용 모니터링", each as a whole word
("토큰 소비" is not "토큰 소비자"), and only when the sentence's final
predicate asks to see the usage -- show, tell, check, compare, monitor,
track, how much, how is it, a report, or "is a lot" / "is fast" -- or the
sentence ends on the phrase itself ("이번 주 토큰 사용량"). The final predicate
is the last word, or the word before it when the last word is the
auxiliary written apart ("보여 주세요", "알려 줘", "확인해 주세요") or a spaced
ending matched whole ("모니터링 해줘", "추적 해 줘", "얼마 나왔어"), so 해제해줘
and 하지마 are predicates of their own. Every other final predicate leaves
the phrase uncounted: work (만들어줘, 추가해줘, 고쳐줘, 파싱해줘, 작성해줘, 짜줘,
줄여줘), so "토큰 사용량 API 만들어줘" and "토큰 사용량 버그 고쳐줘" stay on
ultrawork, and any other question shape too. A modifier earlier in the
sentence ("기능별 토큰 사용량 알려줘") does not stop a usage question. The
guard's English-shaped token arm is unchanged: 토큰 or 비용 beside 보여줘,
상태 or 요약 still opens the card, as on main ("토큰 사용량 제한 로직 보여줘",
"토큰 사용량 요약해줘"). So does a how-to or a check under a report predicate
("토큰 사용량 파싱하는 방법 알려줘", "토큰 사용량 버그 확인해줘"), as on main,
where English asks or answers directly. Usage requests whose final
predicate is outside the report set no longer reach the card; this is a
class, not a list. Measured examples that dispatched it on main and now
ask: "토큰 사용량 어떻게 돼?", "토큰 사용량 얼마나 돼?", "토큰 사용량 궁금해", "토큰
사용량 확인 가능해?", "토큰 소모 심하네", "에이전트 비용 추적해줘", "오늘 LLM 비용
얼마 나왔어?", "이번 달 API 비용 얼마야", "이번 달 비용 얼마 나왔어" and "토큰
얼마나 썼어?"; "토큰 사용량 리포트 만들어줘" dispatches the
greenfield interview. English asks or answers directly on the same shapes
("how is my token usage?", "how much did the API cost this month"), and
questions about what was spent belong to Hermes' /usage and /insights per
the card's Do-Not-Use. Measured with
build_chat_interaction_payload (source="discord"), awareness_route_hint
and the skill candidate line at main and at this head, over both corpora
(unchanged except three English llm-wiki clarifies whose leading candidate
moved), the triage probes, 134 Korean probes of our own and the review's
probe sets: Korean diagram requests that dispatch codebase-uml go from 1
to 5 of 25, plus 4 that now ask with it leading, and no Korean diagram
negative moves toward it; of 21 LLM-wiki requests, which went to wiki (18)
or dispatched the interview (3), 20 now ask and one dispatches
materials-package on "PDF"; ops-observability-card dispatches none of our
24 everyday-sense negatives (20 before), 4 of the review's 52 code and
everyday requests (44 before; the 4 dispatched it on main too), 22 of our
24 usage requests and 31 of the review's 36 (all before). A held-out set of
48, written after the first fixes were chosen, moved the same way:
codebase-uml dispatches 0 -> 4 of 8, wiki reaches 7 -> 0 of 7 LLM-wiki
requests, and ops-observability-card dispatches 9 -> 0 of 10 negatives and
7 of 8 usage requests (8 before). Adds 21 negative controls and 29
interventions.
-
The OMH TUI catches up with Claude Code and oh-my-pi. It reads on a light
terminal: it asks the terminal for its background colour before the first
frame (OSC 11, at most 0.1 s, with COLORFGBG as the fallback) and measures
its theme against it, so prompts and replies are the terminal's own text
colour, every coloured word reaches 4.5:1 and every rule or mark 3:1 on that
background (the status line's against its own bar), words that sat on the 3:1 decoration colour moved to colours that
read, and a light background gets light diff bands (on white the body text
measured 1.08 to 1.13:1 before); /theme auto|light|dark picks the background
for the open session. A slash command is echoed as > /name arg and what it
prints stays in the transcript under it, a long output as its first 12 rows
and a count of the rest for /history; nothing a command prints opens the
pager any more, so typed-ahead keys are no longer swallowed and the output is
still in scrollback afterwards. Hermes' own notices (notification.show:
the agent still starting, credit warnings) show on one row above the
composer, replaced by the next, withdrawn by key, or gone after their time,
where they were dropped before; and a refused call reads as words (/undo on
an empty session: No user messages to undo. instead of
command.dispatch failed (4018): no user messages to undo). Agents show in
one place: the HUD panel's [Agents] block steps aside while the strip and
the list hold agents (the panel said "2 running" minutes after both had
finished), agents whose goals start alike are numbered on the strip, and the
status line says idle · 2 agents running while agents outlive the turn.
Mouse reports are on only while the agent list is open, so during a turn the
wheel scrolls and a drag selects; the strip is reached with Down. Up and the
new Ctrl+R search reach earlier sessions' prompts: the TUI reads Hermes' own
input history ($HERMES_HOME/.hermes_history, the file hermes --tui
keeps) and appends each line you send to it in that file's format, opened
append-only and without following a symlink, created mode 0600. Esc twice
clears a draft into the session's history, or, on an empty composer between
turns (and /rewind), lists your prompts: the one you take comes back to
edit, and sending it truncates the session before it (prompt.submit with
truncate_before_row_id and confirm_truncate) and redraws from the cut.
A line that starts with ! runs in Hermes' shell (shell.exec, 30 s at
most, dangerous commands refused) and shows > !cmd with its output and
exit code; it never reaches the model, and during a turn it waits in the
queue. A paste of more than 3 lines or 800 characters is one atomic chip,
[Pasted text #1 +60 lines], sent whole and shown compact in the
transcript. The working row counts the turn's tokens, each turn ends with
✻ 34s · 3 tools · ↓1.2k, a turn of 10 s or more ends with the terminal's
notification (OSC 9, OSC 777 or the bell; OMH_TUI_BELL=0 silences it), and
the terminal title names the session and its state. A tool row shows the
first three lines of what the tool printed (a failed one its error's first
line, or the last three lines when only its exit code says it failed), and Ctrl+O opens the whole transcript with every detail. In the agent
list, x twice interrupts the highlighted agent and s steers it with the
next line you send. The plan panel follows Hermes' todo.updated at once
instead of waiting 2 to 8 s for the HUD's next poll. Every repaint is one
synchronized update (DECSET 2026). While Hermes asks something, the mode row
names that question's keys, and neither row offers Esc for an interrupt
while anything else takes Esc (a question, a picker, the search, the agent
list, a picked steer or rewind, a draft); the strip ends with ↓ agents; a narrow approval keeps a key hint
and a wrapped command its indent; the banner is one row (the model is on the
status line, the keys on the mode row) and a fresh session names the last one
with its /resume command. Claude Code's names work: /cost and
/permissions run Hermes' /usage and /approvals, /todos prints the
whole plan, bare /model opens a picker of the models Hermes offers and
switches this session to the one picked (it printed the current model
before), and /export first says that Hermes exports a profile archive, not
the transcript. Alt+Backspace (and Ctrl+Backspace) deletes the word before
the caret, and Alt+B and Alt+F move by a word under the kitty keyboard
protocol too, where they did nothing. A start on a terminal of 100 columns
and 24 rows or more shows the OH-MY-HERMES block logo above the banner, from
the shipped skin and in its gradient, lifted to read on a light background.
Motion follows one rule set: a reply opens with ⏺ in the text colour and
a tool call's name in the tool colour; a running tool's ⏺ pulses (each call on
its own clock) and settles to ✓ or ✗ before it reaches scrollback; a
highlight sweeps across the working row's verb; OMH_TUI_REDUCED_MOTION=1
or NO_COLOR holds everything still and repaints once a second. Your
prompt sits on a tinted band to the right edge (an erase in that background,
so a copy picks up no spaces), a prompt the queue sent says ⧗ from queue,
and a steer shows as ↪ steer · <text> under what is running until Hermes
answers; its row then lands at the next block boundary. A steer answered
while a tool ran used to close the tool group and mark the running call
▪ cut off, and one answered mid-reply split the reply in two. A command
typed during a turn (its echo and output) and the agent list's steer and
interrupt rows wait under what runs the same way, and two commands out at
once each print under their own echo. Each turn's
done line sits on a thin rule to the edge, and the answer you gave an
approval is written above the call it was about, ✓ allowed once · <command> on a light green band or ✗ denied · <command> on a light red
one; failed and denied tool rows with their lines and error notices sit on
the red band too, a denial shows the one red ✗ (no amber ⊘), and with
no background reported nothing is banded. A turn's last lines and its done
line sit right above the panel on a full screen, where blank rows used to
stay under them, more the taller the last tool group was (23 for 12 calls
at 40x100; origin/main had the same gap).
A call Hermes only drafted (tool.generating) and never started, such as a
streamed attempt it discards and retries, leaves no row and is not counted
in the done line, where it settled as ▪ tool_call; a deferred tool's
tool_call draft becomes the call it reached. The plan header's parallel shot ×N badge, and the desktop pane's chip, show only a count of 2 or
more, so calls run one after another no longer read parallel shot ×1.
The composer wraps between words instead of splitting a word at the edge,
as the echo of the sent prompt does, with one difference: a space stays on
the row it ends, so a word with no room left for the space typed after it
moves to the next row (the echo keeps the word there and drops the space),
and a tab with no room takes a row of its own.
While you pick from a list, the composer is hidden, as in Claude Code: an
approval, a clarify question with choices, and the /sessions, /rewind
and bare /model pickers stand where the composer was, with no rules (a
picker keeps the caret at the end of its filter row, where its typing
goes), and the draft comes back as you left it when the list closes (a
question waiting behind the first opens before the composer is drawn
again). An approval lists deny, allow once and allow this session one per
row, deny highlighted (❯); Up and Down move as Left and Right do, stop at
either end so Up then Enter still denies, and no number picks one. A
clarify question numbers its choices and ends with Other (type your answer), Hermes' wording; that row, or any character that picks nothing,
opens the composer as the answer field, and Up or Down goes back to the
list. A picker's filter is its last row. A clarify or sudo answer used to be
typed into the composer in place of the draft, which came back as plain
text with its caret at the end: a paste chip in it no longer expanded, so
sending it sent the chip's label instead of the pasted text.
-
A portable host is no longer told to load a skill only Hermes ships. On
main the Agent Skills bodies and references named 17 such skills 63 times:
by label (omh-research-department), by backticked or hyphenated canonical
name, or by a one-word name right after "route to" or "routed to". None of
these remain. A Do Not Use When line that hands its request only to such
skills now keeps the request and loses the pointer, so the skill still says
what it is not for. The rule reads the shipping set, so the pointer comes
back once one of its siblings ships portably. Every other sentence is
rewritten for that projection only: a list line through the new
PortableLine, which keeps its portable wording beside the Hermes text; a
description or other single-text field through portable_overrides (the
portable frontmatter now reads a description override); and the wiki
blueprint reference through PORTABLE_REFERENCE_REWRITES. A gate reads
which skills each projection ships and fails, by path and line, when a
portable body or reference names one the portable projection does not ship.
A second test fails when a skill that a rewrite leaves out starts shipping
portably, so the rewrite is re-read. Hermes bodies, references and their
digests do not change.
-
A host turn or a thank-you gets a direct-answer card. omh chat route-hint and the example shims showed the generic no-hint card, with "Open
omh" and "Clarify" buttons, beside a route decision that said to answer
directly: on a turn Hermes wrote from one of its session-command templates, on
"thanks!", and on every other route the router answers in chat. Where the hint
rail had named a workflow beside such a decision, the card offered to open it
("how long does it take to become a doctor" offered omh-doctor). The card
could not tell these routes apart: the compact route_decision it reads cuts
the reason to thirteen characters. The router now names each answer-in-chat
fallback with a stable reason_code (direct_answer, host_command_turn,
native_loop_cadence, typed_loop_goal, loop_construct, and file_lookup)
on the route and on route_decision. The key is additive and absent on every
other route, and reason keeps its prose. A direct-answer code gives a new
direct_answer_route_hint card with no actions and no tool checkpoint, which
says no OMH workflow is needed; its next_backend_commands no longer lead
with a hinted workflow, and the human omh chat route-hint summary reads the
card instead of the hint beside it. The router's next action, claim boundary,
clarification and routing instruction, and the wrapper's file-lookup and
direct-answer cards and its loop-timer check, read the code instead of
matching the reason's wording. A turn Hermes wrote around an OMH status,
quickstart or intro question ("omh status" under a /plan or heartbeat frame)
became that OMH card in omh chat interact, beside the router's decision to
answer it directly; it now gets the direct-answer card the router decided, as
it already did for a catalog question. Where the wrapper does turn a route
into an OMH card, it drops the replaced reason's code from the route and from
route_decision. Measured over both corpora on Discord, plus 18 messages on
four sources, at origin/main dc6933c3a and at the head: no route,
interaction card or next action moved. The route-hint card moved on exactly
the 271 direct-answer routes and nowhere else, and its backend commands on the
58 of them where the hint had named a workflow. Of the 271, the 211 corpus
rows are all negative controls, 165 from the no-hint card and 46 from a
workflow card. Over four Hermes frames around six OMH questions on four
sources, the interaction card moved on the 72 host turns that had become OMH
cards, and on none of the same questions typed by a person.
host_owned_command_turn, a pass-through over the bundle's
host_command_turn, is gone; the router and both wrapper payloads call the
bundle's predicate.
-
spend-gate and data-share-review admit the same requests on the router
and the in-session hint, whatever courtesy opener is used. Four readers
of a request's opening -- spend-gate's clause rule, data-share-review's
lead, the loop-on-a-timer verdict and the router's command word -- each
kept their own list of openers, and the lists had drifted: "hey, redact pii
in the export before we send it to the vendor" reached data-share-review
and the same sentence opened with "hi,", "pls" or "would you" did not. One
bundle list, request_lead.COURTESY_OPENERS, now serves all four; a "."
right before a "/" stays with what follows, so ok./loop keeps OMH's
sigil. "pls", "plz" and "kindly" mark a spend as "please" does, and so
carry its known residual: "pls pay with my card in safari is broken"
reaches the gate as "please pay with my card in safari is broken" already
did. "hermes," before a data-share request is the address it is for
spend-gate; Hermes named after it still withdraws the review ("before
hermes uploads it"), a trailing ", hermes" included, and the docstring now
says so instead of claiming only a Hermes setting does. The hint also
stops naming spend-gate where the router withdraws it: the everyday-sense
pair for its cap and wallet phrases moved from the router into
spend_signals, whose clause rule applies it, so "can you check out the
spending cap for the city council budget" gets no gate on either surface.
A loop's prompt and the gate named as a command are exempt on both
surfaces, as they are from the request marker, so "run spend gate on my
spending limit" dispatches the gate instead of a clarify without it. The
gates' spaced names ("spend gate", "data share review") are no longer
direct invocations for the hint, which follows the router's verbs ("use
spend gate") and the hyphenated names. data-share-review's hint reads the
router's own trigger table as whole words, so "anonymize the dataset
before we upload it to the provider", which the router dispatches, gets
its hint and arms awareness on a later turn. Measured with
build_chat_interaction_payload(source="discord") and
awareness_route_hint at dc6933c3a (identical on every row to the
branch's first base, cd8a879db) and at this head over both corpora, the
follow-up probe sets, every string in the two skills' test files and a
matrix of 33 openers over 17 requests (2,632 sentences): neither corpus
moved on the router or the hint; router/hint agreement on whether the gate
is offered went from 260/281 to 297/297 for spend-gate and from 61/78 to
152/154 for data-share-review (the two left are one transcript-excerpt
sentence, in two of the sets, that the router dispatches to its owner,
media-input-operator). Outside the two gates, an opener new to a reader
now reads as the bare request does, or as the request after "please" for
an opener that marks one. Behind 11 openers over every corpus case that
opens with a Latin word (12,740 routes), 166 routes outside the gates
moved and 161 now match that reference: 76 requests that open on a fix,
build or change verb, behind "hey,", "hi,", "so", "just", "let's" or "i
need you to", dispatch (46) or ask (30) with ultrawork leading, where they
went to feedback-triage (30, among them three negative controls such as
"fix the broken wheel on my shopping cart") or a clarify led by another
skill; 12 cadence reports behind four openers each
(48) clarify instead of dispatching automation-blueprint; loops on a timer
get Hermes' /loop (20) or, after a cadence naming ulw-loop, OMH's loop
(8); and two pay-on-my-behalf feature requests after "pls" and "kindly"
clarify as after "please" (2). The other 5 are "configure web search"
after "hey,", "hi,", "so", "just" or "let's", which now asks with
websearch-setup leading, as "please configure web search" does, where the
bare request dispatches websearch-setup (before: dispatched web-research).
The money cues of a send or transfer are read as words, so "please
transfer the balance with my card-on-file" stays admitted. Internal: one
offers-itself table row per gate, spend-gate's clause tokenized like every
other skill's message, and the misleading _WHOLE_WORD_ROUTE_HINT_RULES
replaced by the hint's phrase readers.
-
Every skill says one thing about spends, retired siblings, review
retries and the one plan checklist. A loop step that would move money
goes through spend-gate first while the loop carries on, in that skill's
own terms: an agent run on a schedule never spends, and a no-agent script
that pays is a spend set up now. ultraperf stops sending a declared metric, baseline
and benchmark to performance-goal, a skill #1691 folded into ultraperf
itself; a declared goal starts from its baseline there, as its recovery note
already said. decision-prototype's compact body now carries the line that
hands a multi-question feasibility probe to Hermes' bundled spike, which
only its on-demand full contract held. code-review's two references agree
on a failed review return: when the host checked the return against the
schema, the same reviewer is not asked again, because Hermes' completion
message carries no retry count to wait for. The route hint's plan_todo
line and the context tool hint name all three plans only omh_todo holds (a
planning run, an accepted plan or a code-story template), so a code-story
run is no longer pointed at todo_list, whose write would be held. The
grounded-citations ledger and verify rule, the blocked-page recovery note,
the curator-ledger reading rules, report-package's powerpoint rungs, the
native-tool presence clause and the shared-rail pointer are each one string
their skills compose, where they had been retyped.
-
Memory recall no longer fills a pack with records that share only the
project's name. A query term that more than half of the records the pack
could serve hold, when there are at least five of them, never makes a record
match on its own. A subject's replaced values, stale records shown only for
inspection, and extra copies of one summary are not counted. The term still
orders records of equal coverage, a record that carries it as a tag still
matches on it, a subject's current value that shares it still takes an older
value's match on another word, and a query whose every term is common keeps
them all. A record that met the query only on such a term is excluded as
common_terms_only, and that overlap no longer triggers the active-tier
fallback; a query that overlaps nothing, or overlaps only through stemming,
still falls back. It is not idf, and a rare term gains nothing. Measured
against origin/main at 03741a6a8 by replaying the 2026-10-14 memory A/B
store (21 records, 11 tasks) through the prefetch selector: the two control
tasks, which no record answers, served 12 records before and 4 after; each
of the nine memory tasks kept its record in the pack, and one more of them
now leads with it. On blind rounds 3 to 6 and their tie-flip twins (176
cases, the lead-record rule), 0 wins, 176 ties, 0 losses; one round-5 case
and its twin now hold back a second topic record that shared only the common
word. Those rounds were seen while choosing the rule.
-
What a Hermes background-review or /btw fork still does to OMH on the
0.21.1 plugin floor is written down, and the floor stays at 0.21.1 (a #2112
follow-up). On Hermes 0.21.1 such a fork's turn end still calls OMH's
on_session_end under the person's session id, and that call carries no
parent_session_id; Hermes 0.21.2 stops calling it for a fork. CONTEXT.md
now defines the Detached fork and records what that turn end does,
measured by calling OMH's hooks with the arguments the fork sends as read
from Hermes source. A route written during a Hermes turn stays in place,
because the restore is scoped to the task that wrote it and the fork's task
id is its own. A route recorded without a task id but under the person's
session id is put back at the fork's turn end. The metadata-only
plugin_session_end checkpoint can carry the fork's time. None of it was
observed on a live 0.21.1 host. The entry also names the tool hooks a fork
reaches on every release, transform_tool_result included, and the
unbuilt OMH-side fix (correlating the turn id pre_llm_call saw). Raising
requires_hermes to >=0.21.2 was rejected because it would drop every
0.21.1 install. Docs only; no code changes.
-
On a gateway turn OMH routes on the person's own words. With Hermes'
Discord tools loaded, every Discord message reaches OMH behind
[Triggering message id: `…` — use as `message_id` for reply/react/pin via the discord tools.]; a reply adds a pointer that quotes the message replied
to, a channel can add backfilled history before [New message], and a shared
session puts [<name>] before the text. The in-session route hint, the
candidate line, the chat router and the wrapper read all of it as the
request. On origin/main 42ad99ec7 the trigger note alone changed the hint on
102 of 787 intervention cases and 41 of 748 negative controls, and the route
on 159 and 404 of them: "please pay with my card for the summary report" went
to gateway-intent-card instead of the pre-spend card, and "what is a web
crawler" dispatched web-research. One helper, person_request_text, now
removes that material before any route is decided; a reply's quoted text is
context, not the request. What OMH hands on still carries the whole turn: the
routing prompt a bridge forwards to Hermes, the coding handoff and the plan
keep the quote, an attachment's path and the backfill. The sender prefix is
removed only on a turn from a messaging gateway (the platform in the hook,
the discord, slack or telegram source in the router and the wrapper),
since Hermes writes it nowhere else, and even there a bracket that names a
skill, omh or ulw, an invocation, a relay header, or a second bracket
stays: [omh] status, [deep-interview] … and [ulw] fix the flaky tests
route as before on every surface. A role marker is read from the person's own
text. A reply pointer ends at the "] after its quote and an image
description at the ~] after its closer-look note, so a ] and a blank line
inside either no longer cut them; QQ's [Quoted message]: block, which has
no close, leaves the turn whole. The context brief and the plugin tools'
standalone fallbacks now skip a turn Hermes wrote from a session-command
template, as the hook and the wrapper already did. Measured over both corpora:
behind a trigger note, a reply pointer in either Hermes order, or a reply
quoting a skill request, nothing differs from the bare request on the hint,
the route or the wrapper's next action; behind a sender prefix on a
messaging turn, only a request that itself opens with a bracket differs, and
it reads as it did before. Routed bare, no route moved; the hint moved to
none on the 8 Hermes host frames in the corpora, and two loop requests behind
a sender prefix now start the cycle, as the same request without the prefix
does.
-
A refused or Hermes-recovered fanout unit ends in a true state. A unit
refused after a capacity-reuse reservation (no provable write fence, or the
reused worktree's preflight), or one whose dispatch raised before its spawn,
left its in-flight marker behind, so fanout status had to compare write
times to avoid reading it as in flight; every path out of a unit dispatch
that got its worktree now clears the marker, and a refusal for a worktree it
did not get still leaves another dispatch's marker alone. The opt-in Hermes recovery lane
(--on-failure=hermes) sent its file-tools-only child a prompt asking it to
run a verification pass and commit, which it cannot do, and nothing did
either afterwards, so a completed recovery left edits unchecked and
uncommitted. The child now gets an edit-only prompt. What the failed attempt
left in the worktree is committed on its own before the child starts; when
the child completes, the dispatcher commits its edits on the unit branch and,
under --run-verification, runs the unit's declared checks on that commit.
The dispatcher's commits and checks run inside the unit's write fence (the
child does not), and the lane refuses before the child starts when no fence
can be proven or the unit's branch is not checked out. A new file -- a
tracked file moved to a new path included -- is committed only inside the
unit's file_scope; one outside it (a .env, a build artifact) is never
committed and is named in the record, and the lane refuses before the child
when the failed attempt left one. The attempt's
unit_state is verified only when the child changed something, all of it
was committed, and those checks ran on it and passed. fanout status --wait's documented codes and bounds, and the deadline ulw-maestro names,
are now pinned by parity tests against the command's constants.
-
A profile is served only its own consolidation brief, and
plugins.entries.omh.settings.dreaming_mode turns the brief off for that
profile (#2087). Profiles that bind one OMH store, such as every profile of
a gateway running gateway.multiplex_profiles: true against ~/.omh, shared
one memory/dreaming.json and one memory/consolidation.json. A nearly full
MEMORY.md in one profile raised a brief that every other profile was then
served on every turn, and all profiles' turns moved one interval counter. The
counters and the brief now live under
memory/profiles/<sha256 of the Hermes home>/ (the slot the group-activity
status already keys by). The pack, the chat notice, omh_memory, omh memory dream and omh doctor read the brief of the Hermes home they are bound to.
Measured with two profiles on one store, profile A over its headroom floor,
20 interleaved turns each. Before, B's pack carried a brief on 20 of 20
turns, 14 of them with A's headroom_below_floor reason. The shared interval
fired 6 times for B and once for A, and A raised a brief led by its headroom
reason 6 times, because each brief B raised replaced the last_reasons that
suppression compares against. After, B's pack carries A's reason on 0 turns,
each profile's interval fires 4 times in its own 20 turns, and A's
headroom-led brief is raised once. dreaming_mode: off in
a profile's own config.yaml stops that profile's brief from being raised,
served or reported, including one written before; bare off and false
both mean off. Unset keeps reminder, the default. Any other value, or a
config OMH cannot read, also keeps reminder but is reported as
mode_setting_unrecognized, in omh memory dream's mode_setting and as
omh doctor advice. On the first attended session start after the upgrade, a
single-profile host moves its old home-wide files into its profile directory
and keeps a pending brief. Two cases leave them unread: the profile already
has its own files (omh memory dream --evaluate raised a brief first), or
the profile is routed, which every profile of a multiplexed process is, even
a single profile under gateway.multiplex_profiles: true. omh memory retire --apply retires an expiring-only brief in every profile's directory. Thanks
to @kanzaka110 for the report and @sanjkrsna for pointing at the
per-profile key.
-
omh install --force reads Hermes' curator ledger once, and names the
ledger it could not read when it reports what a removal lost. Under
--force the install read and parsed the whole ledger again for a replaced
Hermes edit, again for a skill it cleared, and again for every retired
directory it removed, beside a comment saying it read the ledger once. The
read it already made now also keeps every write the ledger records when a
local change may be overwritten, and each of those reports takes that list.
On a synthetic 190.8 MB ledger (16,000 rows in the shape Hermes wrote before
0.21.4, 20 files each, 30% of them under the OMH pack), a --force install
that replaced two skills and removed three retired directories went from 6
ledger reads in 8.1 s to 1 read in 2.9 s with the same result; a --force
with nothing to lose went from 2.9 s to 2.7 s, and a plain install from
2.3 s to 2.0 s. With no row under the pack, that --force with nothing to
lose is slower, 0.19 s to 0.54 s, because it now parses every row where it
used to skip them all, while the one that replaced and removed went from
5.4 s to 0.54 s. When a ledger could not be read, each replaced edit or
--force removal that lists what Hermes still holds a copy of carries
ledger_copy_partial: true, and one summary line after those lists names
what could not be read and says they count only what could be; a --force
removal OMH could not judge for that reason now names it too, and a
--dry-run result carries unreadable_ledgers. A ledger with more than one
torn line is named once, with a count, instead of once per line. The ledger
reader no longer drops every write when given a generator of directories,
resolves those directories once per read instead of once per write, and
builds a row's after list once instead of once per file the row listed
before; omh doctor judges Hermes edits once instead of twice.
-
A checked team no longer checks a part while its helper's work sits
unmerged in the worktree Hermes gave it, and the board fan-in asks Hermes
only for transitions it lands. With Hermes' delegation.worktree_isolation
on, an omh_team helper edits a worktree of its own, and its work reaches
the session's workspace only when the session merges it. team_reconcile
still ran each part's check in that workspace, so a check could pass on a
tree without the part's work and accept it. It now reads each returned
helper's branch (hermes-subagent/subagent-<id>, from the subagent id
Hermes' subagent_start carries) and its worktree (.worktrees/subagent-<id>,
found by path even when the helper left the branch for a detached HEAD or a
branch of its own) with read-only git. While the branch's last commit or the
worktree's HEAD is missing from the workspace's history, or the worktree
holds uncommitted changes or untracked files, it checks nothing and is
refused as helper_branch_unmerged, naming each branch in unmerged. OMH
never merges. A branch git cannot read makes that part's check
inconclusive, so the team still reaches a stop. Work held by neither the
branch nor the worktree (a branch renamed or deleted after its worktree was
removed) is not looked for, and a host that names them differently leaves
the guard off.
The helper's own instructions no longer say the workspace is shared: they
say the check runs in the parent session's workspace, and that a helper in a
worktree of its own commits on its branch. In ultraqa's board fan-in
reference the main session no longer prepares request_review on a done
fixer row or request_changes on a row no review run holds, both of which
Hermes refuses: the fixer's own run ends with kanban_request_review, and a
failed re-check this session ran is a comment on the row, with sending it
back left to the operator's hermes kanban reopen-review.
-
omh_gather_evidence bounds the paths a probe's arguments name. The
allowlist matched a command prefix and left the rest free, so
python3 -m compileall /any/path compiled files anywhere and printed their
paths and the source line of any syntax error (#2137, reported by
@simongonzalezdc). A compileall argument, the value of an omh option that
opens a path, and a git diff path argument must now be relative, free of
.., and resolve inside workdir after symlinks; a path refusal names the
rule, never the path or where a symlink leads. compileall also needs at
least one such path, because with none it compiles every directory on
sys.path; it refuses -i (paths read from a file or stdin), -b
(bytecode written beside the sources, past the private pycache) and
-d/-s/-p; and it runs with -e ., so a symlink below a compiled
directory that leads out is skipped, and with PYTHONSAFEPATH, so a
compileall.py in workdir no longer runs in place of the stdlib module
(Python 3.11 and later; an older python3 ignores it).
git diff refuses -O (an order file read from anywhere), and its path
bound stops the switch to --no-index that two paths with one outside the
repository caused, which printed both files; a :/ pathspec or
<rev>:<path> still reaches the whole repository, as a bare git diff
already does. omh doctor refuses --profile-isolation, and
omh release evidence-bundle refuses --write and a --verify PATH.
Evidence probes and omh_team checks now run with no stdin.
-
The plugin's route hint reaches the router in Hermes chat, so your own
trigger packs hint there too. Hermes imports the plugin bundle as
hermes_plugins.omh, one package deep, and there the bundle's
from ...routing imports climb past the top-level package and raise
ImportError even when Hermes can import omh. Four of them had no absolute
fallback, so in every Hermes chat the bridge to the router for user trigger
packs (#1539) returned nothing: a phrase from
<omh-home>/routing/trigger-packs/ got no_hint from the plugin while
omh chat route-hint hinted it. Coding-delivery hints also asked the user to
choose the executor instead of carrying the router's owner decision, and the
visual-QA and office-material cue tables were the bundle's copies. Each import
now falls back to its absolute omh. form, and the bridge still resolves on
each call. Over both routing corpora (1,535 messages, measured against
42ad99ec7), the plugin's hint with omh importable differed from the package
layout's on 118 messages before, each in the coding-owner decision, and on
none after. Where Hermes cannot import omh, the usual install, nothing
changes; docs/INSTALLATION.md now lists the trigger-pack hint and the coding
owner among what that turns off. A test loads the bundle under Hermes' own
package name, and a gate requires every bundle import that climbs above the
bundle root to be paired with its absolute form and, at module scope, to bind
the router's object there. Reported with a reproduction by @fauzibrevy-hub
(#2129).
-
omh coding status-board shows Hermes' delegate children and kanban
workers beside the fanout units. The board listed only fanout units, so the
command could not show the work omh_hud already showed. It now reads the
same two readers the HUD uses (hermes_delegation over state.db,
kanban_board_reader over kanban.db), opening both read-only, and lists
each worker with its source and state in a second table under one headline.
The rows keep the board's running-first order, and a kanban lane whose
heartbeat stopped is counted with the stuck units. A Hermes database that is
missing, unreadable, refused or read only in part prints a line saying so
instead of an empty list. To tell those cases apart, both readers now report
a read_status, which the HUD payload does not carry. A reader that reaches
its selection bound now says so (selection_capped), and the board then
shows its counts as lower bounds ("at least 96 running") instead of as
totals. A kanban lane that never started reports no elapsed time instead
of 0; the HUD still draws it as before. The fanout rows render as before.
The run-efficiency route reason now says the report reads the supplied
timings and context budget plus Hermes' recorded usage for a named session,
with provider, billing and cron not observed; it still described the
supplied-metadata report from before #2114.
-
omh chat route-hint names no workflow on a turn Hermes wrote for its own
session command. On such a turn (a /plan frame, a /loop wakeup, a
/goal continuation, a heartbeat, a goal-mode kanban nudge, a /blueprint
seed) the route decision already said fallback, but the hint beside it was
read from the frame's text and named a workflow: the /plan frame came back
hinted command-operator, and each of the 16 seeds Hermes' own
build_blueprint_seed writes for its built-in blueprints automation-blueprint.
The hint now reads no request on such a turn, as the plugin's pre_llm_call
hook already did. Measured against origin/main at 03741a6a8 over both
routing corpora, every host frame behind each gateway prefix, and the
frames' bodies without them (1,678 messages): 101 hints moved to none, every one on a host turn, and no route
decision moved on either payload. The router's reason for these turns no
longer lists commands, so it cannot fall behind the frames OMH recognizes (it
had left out /blueprint and /initiate-setup). The spend-rails.md
reference both targets ship no longer names OMH's browser adapter, which
another host does not have; the Hermes body still does.
-
The OMH TUI keeps the keys typed right after Esc, and stays fast in long
sessions. Esc followed by a key within about 50 ms lost both keys (Esc then
/quit left quit in the composer, for Enter to send as a prompt); a
character sent in the same burst as an Esc now types (tmux before 3.5 sends
them that way), and Esc then a key in separate reads acts as both. Option+←
and Option+→ in macOS Terminal.app move by a word. A bracketed paste whose end
marker never comes ends after 0.5 s of silence instead of swallowing every
later key, Ctrl+C included; for the second after, or while the rest of it
keeps arriving, a line break adds a line instead of sending the prompt. /new
no longer keeps a resumed session's banner for the next redraw, and an image
Hermes attached (/image, /paste, a drop) after you left the session it was
sent for is a notice instead of a chip in the new one. A call the gateway
leaves unanswered for 120 s (Hermes' own TUI's limit) is dropped, with a
notice for one a person waits on. A full redraw (a resize, Ctrl+L, /redraw,
a switch or a resume) prints the last 3,000 rows under ⋯ N earlier messages · /history shows all, and /history renders a page at a time. The TUI holds a
session's last 2,000 messages and the composer its last 1,000 prompts, and an
edit's diff is held as its UTF-8 bytes (one 200-line truecolor edit: 16,508
bytes, 28,558 as parsed lines). Measured against origin/main at 14cc8731a
with the review lanes' in-process harnesses (load average 10 to 30): at 1,000
turns a redraw took 14.8 s and 118 MB at its peak and now takes 0.27 s and 4.5
MB, and /history opened in 5.7 s holding 65 MB and now in 6 ms; a key in a
500-turn session takes 0.19 ms (was 1.35), a key in a 2,000-line paste 13 ms
(169), Up there 0.35 ms (254), a spinner tick over a streaming
20,000-character paragraph 0.26 ms (40), and a tick with an agent's 400-row
log open 0.06 ms (95). The loop wakes for gateway events and HUD changes
instead of reading every 50 ms: event to frame 0.1 ms median (30), and an idle
TUI wakes about once a second (19). Bare omh reaches hermes in 46 ms (445)
without importing its command tree, and the first frame no longer waits for
the busy-mode read. A HUD read over 5,000 run directories checks only the runs
it shows and reopens only binding files that changed: 190 ms (708).
-
Skill text decides which skills are OMH's by the installed label, and the
spend, browser, schedule, and parallel-tool skills say what Hermes does.
skill, rules-distill, and skill-health no longer treat any omh-* or
ulw-* name as OMH's: one shared sentence says an OMH-managed skill is one
OMH installed under a label its catalog renders, and a companion the person
or an agent created is theirs whatever its name. The skill_manage refusal
suggests a companion name without OMH's prefix (plan-notes for
omh-plan). parallel-tools reads each MCP server's
supports_parallel_tool_calls and offers that flag, with an update only on
request, instead of describing a version-currency check. A recurring job or
a page step that would move money goes from automation-blueprint or
browser-operator to spend-gate; loop sends an unattended schedule
through automation-blueprint instead of straight to Hermes' cron tool; and
browser-operator carries the unattended-run rule the other operator skills
state, with Hermes' card prompt recorded beside the spend gate's typed yes.
command-operator and spend-gate say what Hermes does with a
pending_approval command at v2026.9.7 and on upstream main: it is stored
and never run, and /approve resumes only a run still waiting on an
approval. spend-gate's portable body drops the hermes chat -q
parenthetical, the OMH browser adapter line, and the pending_approval rule,
which a host-neutral held-command rule replaces; prose that named a sibling
by its catalog name now writes the label skill_view loads, and the spend
and data-share references name only states their skills keep.
-
A /blueprint seed is Hermes' turn, and a spend is spend-gate's wherever
it is asked. When /blueprint matches, Hermes rewrites the turn to a seed
that asks for the blueprint's settings and then creates the cron job
itself; OMH now reads that seed's frame as a host turn, so it gets no route,
no route hint and no candidate line, where before it dispatched a file,
toolbelt or observability skill. A person typing the seed's first line alone
still routes to automation-blueprint. A loop on a timer whose prompt spends
the person's money ("loop every hour and buy the tickets for me with my card
if they drop under $50", or the same as a typed /loop 1h ...) opens
spend-gate instead of being answered with Hermes' /loop, since a scheduled
run never spends; Hermes' own /loop wakeup turn is unchanged. Naming the
gate as a command ("use spend gate") now asks for it. The router, the route
hint and the awareness markers read one phrase table for the gate, so "go
ahead and pay the 402 challenge for the dataset" no longer hints a research
skill while the router opens the gate. A renewal, tip, booking,
subscription, donation or top-up paid "from my wallet" is no longer dropped
as everyday wording, and paying with the person's card, or reviewing the
pre-spend card, no longer opens the image-card skill, while an image card of
"my card game stats" or "my card collection" still does.
-
Memory recall no longer lets a colloquial query's particles, endings and
fillers decide which record leads. A Korean query run loses the particles
and request or verb endings it ends in while two syllables stay (자동으로 is
scored as 자동, 확인해주세요 as 확인, 경로 stays whole), and a run that is
one of them whole (해주세요, 에서 after a Latin word) adds nothing. Korean
discourse fillers, intensifiers and demonstratives (그냥, 진짜, 그거 ...),
English hedges (honestly, literally, kinda, really ...) and the Japanese and
Chinese wrappers って, なってる, 什么时候 and 一般 join the closed query-side
lists. All of them still order records of equal coverage; records are
tokenized in full. The strip never makes a query fall back to every word
(which would promote 어떻게 or "what" to content): the unstripped content
is tried first, and a two-letter word written in capitals (PR, CI, DB) is
scored as a name, so "what about CI" no longer falls back either.
Measured against origin/main at 4d3c10141 with the
blind-round harness and its lead-record rule (distractor ids sort first, so
a tie goes against this change): round 4, 20 cases, 5 wins, 15 ties, 0
losses; its tie-flip twin 4 wins, 16 ties, 0 losses; round 3 and its twin
0 wins, 20 ties, 0 losses each; the 40-case pre-registered corpus served
identical packs. Those rounds were seen while writing the change. On two
rounds frozen by a writer who never saw the code (24 owner-style cases
each), it scored 2 wins, 21 ties, 1 loss and 2 wins, 22 ties, 0 losses. The
loss is a query whose topic record shared the particle form (모델로) that
now only orders records.
-
Bare hermes is stock Hermes again. With bare omh opening the OMH
TUI, OMH stops styling Hermes' own terminal: setup and update write no
display.interface, display.skin or display.sections, install no
status widget and no skin files, and ask no display question
(--no-omh-tui is accepted and does nothing). The OMH plugin stays loaded
in hermes, so its tools, hooks, memory and skills still work there; the
HUD and /omh-model are the OMH TUI's. An install an earlier version
styled is migrated by the next omh setup, omh update or omh apply,
primary home and every bot profile: a display key OMH's record says it
wrote goes (or goes back to the value consent replaced), an omh* skin
goes with or without a record after a theme the person picked is saved
under the OMH home, and a value the person changed or OMH cannot
attribute stays. The widget and skin files go where a manifest (or, before
the release, the shipped bytes) proves OMH wrote them; an edited one, and
the skin the config still names, stay. A key in a YAML shape the editor
refuses holds the release, and is named, until a later pass can take it;
once a pass leaves none, display_released_at in the write record keeps
later updates from taking back a skin, or a skin file, the person picks
afterwards. plugins.enabled, memory.provider and the registration are
never touched by it. A home left unregistered keeps its config and loses
only the old files. omh theme use now saves to
<omh_home>/tui/theme.json (a profile's own store when it names one) and
the OMH TUI opens with it, omh --profile <name> included; omh theme repair is retired (it says so and exits 0). Where the OMH TUI cannot
start, omh says why in one line and opens hermes --tui for a reason of
the OMH TUI's own, or plain hermes under TERM=dumb, OMH_NO_TUI=1 or
without Node. The hermes_tui_* doctor checks and the post-update
OMH TUI: verdict are retired with the surface they judged, and
omh setup --json moves to hermes_native_setup/v2. See "Returning
hermes to stock Hermes" in docs/INSTALLATION.md.
-
omh quality-evidence agent-skills reports Agent Skills host evidence
per host and scope. For every Agent Skills host adapter, in repo and user
scope, it records five stages (installed, discovered, nominated, loaded,
executed) and never infers one from another. installed is observed by
OMH: it reads the host's scan path under --project-root or --user-home
and compares every file with the omh_host_adapter/v1 manifest; the read
writes nothing. The later four stages stay not_observed with each host's
probe_unsupported reason, since OMH has verified no credential-free,
non-interactive listing command, makes no model call, and starts no host
session. The only host process it runs is the readiness module's approved
--version probe, for a CLI in that probe's set; it runs whenever such a
CLI is on PATH, where readiness ran pi and opencode only as omo hosts.
Each omh_agent_skills_discovery/v1 receipt binds that host version, the
OS, the scan path, the manifest's source_digest, and the pack
catalog_revision; the parser rejects a receipt that fails the checks
docs/AGENT-SKILLS.md lists. --receipts compares an earlier --json run
with the current pack and host versions; an unreadable scan path exits 3,
and a missing root is refused. Built on the stage model, host descriptors
and fixture tests @blrain3 contributed in #2093.
-
Bare omh opens the OMH TUI, OMH's own terminal over Hermes' gateway.
omh runs hermes --tui with OMH's frontend in place of Hermes' Ink app,
so Hermes' launcher still resolves the profile, the resume target and
session ownership, and every model call, tool run and approval decision
stays Hermes'. Finished lines go to the terminal's own scrollback and only
the region under them repaints; once the composer has reached the bottom
rows it does not move when the plan and agents panel, or a question Hermes
asked, grows or shrinks. Nothing is
answered for the person: Esc, Ctrl+C, d or n declines, and allowing a
command takes the arrows and then Enter. When the TUI cannot start
(Windows, no termios, no Node, an OMH that cannot import itself, gateway
drift) it creates a file omh named for that launch and exits 75, and
omh opens Hermes' own terminal. The boundary is in CONTEXT.md ("OMH TUI", "Hermes gateway
protocol"); the gateway slice it relies on is declared in
src/tui/gateway_contract.py. The composer sits between two rules drawn in
the input mode's glyph and colour, over a mode row that names the mode or
the keys that matter now; replies open with ⏺, a diff numbers its lines
in a gutter, and the status line reads brand, model, context, state.
On the terminals Hermes' own TUI trusts with it, it asks iTerm2, kitty,
WezTerm, tmux, VS Code and Windows Terminal for the kitty keyboard protocol
and xterm modifyOtherKeys, and Ghostty for modifyOtherKeys only, so
Ctrl+Enter and Shift+Enter arrive as keys of their own, while every key the
TUI binds decodes as before and so does each Ctrl chord xterm sends as one
control byte (Ctrl+2 a NUL, Ctrl+3 Esc, Ctrl+8 Backspace);
OMH_TUI_KEYBOARD=legacy keeps the plain bytes. Shift+Tab cycles normal,
accept all and plan: accept all turns off Hermes' approvals for that session
only (Hermes' per-session switch, never approvals.mode), is shown on the
composer once Hermes confirms it, or when Hermes confirms neither it nor
the switch back off, and the TUI sends that session an explicit off before
it leaves it, and plan sends each prompt as /plan <text>; where Hermes has
approvals off on its own, Shift+Tab sends nothing and turns plan on and
off beside accept all. Ctrl+T or /effort <level> sets the session's
reasoning effort, Ctrl+Enter or /steer <text> adds typed text to the
running turn (a steer Hermes does not take waits in the queue for the turn
to end), queued prompts are listed above the composer and Up takes them
back to edit, ? or /keys lists every key from the table the docs are
held to, and an approval rings the terminal bell once (OMH_TUI_BELL=0
silences it).
A turn's subagents show as a strip on the mode row; Down opens them as a
list, and Enter or a click opens one agent's read-only log, with mouse
reports on only while an agent is there to click.
-
In the OMH TUI, /reload-skills makes a newly installed skill runnable,
and a turn of unknown gateway events says so. /reload-skills (or
/reload_skills) has Hermes re-scan its skills in the gateway itself, then
reads the command list again, so a skill installed after the TUI started
(omh update, /skills install) runs as /<name> without a restart. The
command list is read for each session the TUI opens, so a project's own
skills follow its workspace; its warning (skill, quick-command or plugin
discovery failed, or skills that run only as /skill <name>) shows once; /help lists Hermes'
commands by category with a count of skill commands and is paged when long;
and completion also matches part of a name, so /uml finds
/omh-codebase-uml. A turn that brings no event the TUI shows, only types
it does not know, gets one notice pointing at omh doctor, whose OMH TUI
check now prints the installed Hermes commit next to the one the TUI was
declared against. omh opens Hermes' own terminal only on exit 75 together
with a file it named for that launch, so a 75 Hermes returns for a reason
of its own ends the launch like any other exit code. The HUD's agent panel shows a
Hermes-native subagent whose session has ended as finished at once, where
it showed it running for up to 150 seconds. A plan item carrying an escape
sequence is stored without it, where the sequence's parameters ([31m)
used to stay behind as text.
-
The OMH status widget and the Hermes Desktop pane keep ordinary
punctuation and drop whole escape sequences. Their character allowlists
dropped apostrophes, commas, question marks and quotes, so a plan item
person's rendered as persons, and they removed only an escape's ESC byte,
leaving [31m behind as text. The widget, the Desktop pane and the OMH TUI's
panels now share one allowlist and one escape rule and render the same text.
-
Temp directories, RFC 4122 UUID directories and Hermes session ids no
longer read as credentials. The opaque-value check took the hyphens of a
UUID, a run of Python tempfile names, or a numbered temp directory among
words for a secret split into fragments, and a path segment that opened with
_ or - (_temp, -Users-name-project) or held an uppercase UUID made a
whole path suspect. A memory capture whose source_ref was such a path
stored it as [redacted] and went to review instead of auto-approval, and
work-resume items and completion summaries carrying one became [redacted].
Over 2,000 generated paths per shape, a UUID directory went from 100%
flagged to 0%, three chained tempfile names from 51.8% to 0%, a Hermes
request dump name from 7.8% to 0%, and a Hermes session directory from 1.7%
to 0%. A value split into fragments beside one of these names is still
caught at the rate the same value is caught with nothing beside it, and
detection over 25,000 generated split secrets moved from 17,571 to 17,568.
-
A new spend-gate skill shows what a spend will cost before the agent
moves any money, and calls it done only on a receipt. It covers every
rail: a card checkout in a page, an HTTP 402 or pay-per-request call, a
wallet transfer, a booking or deposit, a paid data endpoint, and a renewal
that charges again. Before money moves the person sees a pre-spend card
with the payee and its exact origin or address, the item, the total with
fees and currency, the rail, the cap and what remains of it, the refund
terms, whether the spend can be undone, and who approves it (the person
whose money moves), and the person's typed yes in that session is required
whether or not Hermes shows an approval prompt of its own. A host prompt
that appears is recorded beside that yes; one that did not appear, or an
auto-approval, is no confirmation, and a choice picked in clarify counts
as the typed yes. A run nobody can answer -- a scheduled job, a webhook, an
API-server or single-query run, a background worker, or a delegated
subagent -- never spends: it prepares the card for the person's next
interactive turn. A payment set up to recur without the agent (a
subscription, a standing order, a capped auto top-up, a script with no
agent in it) gets its card, typed yes and cap now. A quote is not a
purchase; only an observed order id, transaction id, or receipt header
completes a spend, an outcome nobody saw is unknown and is reconciled
before any retry, a payment Hermes holds for approval (it never runs on its
own) is never re-run or reworded and is recorded as not submitted, and a
declined card is not retried. The cap ledger
keeps metadata only. Hermes' saved-card fill, clarify, and the optional
stripe-link-cli and mpp-agent skills are used only when present;
without the fill tool the person enters the card and the agent never types
one into a page. OMH moves no money and holds no credential. The skill is
guidance only: no hook holds a payment tool call.
Routing is deliberately conservative and closed-world, because the gate's
phrases are everyday words that also name payment features, labels, bug
reports, product ideas, articles and questions. The gate is offered only
when the message is marked as a request outside the gate's own phrase:
"please", "can you", "could you", "would you", "will you", "go ahead", "I
need you to", "I want you to", an address to Hermes, or an amount or "for
me" as the spend's object: outside the gate's phrases and before "at",
"for", "from", "in", "on" or "to", and for "for me" after a word of its
own since the last phrase ("transfer 40 dollars", "buy the cheapest one
for me", "pay for me with my card"; not "pay with my card for $0 orders is
broken", not "book the flight with my card for me never shows up", and not
the "for me" of "buy it for me"). An imperative with none of these -- "pay
with my card for the hotel", "buy it for me" -- routes as before the skill
existed: that recall is given up so "Pay with my card in safari is broken"
never reaches the gate. A marked message still has to lead with the spend:
the sentence's first words after filler, up to the first comma, colon,
question mark, "and", "if", "when", "which", "about" and the like, must
open with a spend addressed to the agent -- "buy", "pay", "order", "book",
"renew", "place the order", "complete the checkout", "use my card", and
the like, not an idiom ("pay attention to the spend cap", "pay a visit")
-- and one of the gate's phrases must be in that clause, each followed
only by the end of the clause or the start of the next ("when it is back
in stock"), "for", "on", "at", "from", "to" or "in", "with" the person's
own card or an amount, an amount, "please", "now" or "right away"; "or"
after the phrase makes a comparison, not a request. "send" and "transfer"
also need money, an amount, or the person's own card or wallet; "did the
payment go through" counts only when the agent paid. The skill scores only
on that clause, there is no boost, and nothing stands down another skill's
guard: a spend dispatches only when its clause scores high on the gate's
own phrases, otherwise the gate leads a clarify, and every other sentence
routes as before the skill existed. The route hint and the awareness
markers read the same clause, as whole words. The bare words spend,
pay, checkout, wallet and their siblings score only inside a
complete phrase, and budget is not one of the skill's words at all.
Budget variances, payment failure, checkout, 3DS and crash reports, a
feature request, browser logins, spend-approval research, checkout test
failures and issue triage, purchase acceptance criteria and a saved-card
settings toggle keep their owners.
-
Session usage and the skill-draft check recognize an OMH skill by its
catalog label, not by the [omh] description prefix (#2120).
canonical_skill_for_label answers from every label the catalog renders or
rendered, retired skills included, and omh quality-evidence session-usage
reads it for a SKILL.md load, a reference-file load, a compaction
placeholder, and a frontmatter name line. A prefixed description still
counts under a name the catalog does not render, so no session that counted
before stops counting. The 3.0.0 entry for session usage, which names the
[omh] prefix as the OMH-skill signal, no longer describes it.
-
A new data-share-review skill prepares a dataset, log, ticket export, or
transcript excerpt to leave the team, and calls it redacted only after the
file that leaves was scanned. It asks where the file goes and what that
destination needs, classifies every field as a direct identifier,
quasi-identifier, secret, free text, or not personal, reads a row only when
per-column shape counts leave a field unclear, drops what is not needed
before masking anything, and keeps any pseudonym mapping at a local path
outside the shipped file. The verdict is redacted only after an observed
residual scan of the exact file that leaves counts every class, free text
included; without one it is not_observed. Counts come from Hermes'
search_files in its count mode or a detector script run through
execute_code that prints counts only; that script's stderr and any
traceback return too, so it catches its own errors without echoing a value.
The skill says plainly that Hermes' privacy.redact_pii and
security.redact_secrets cover gateway chat identifiers and tool output,
never a file that leaves. What left is recorded as metadata only:
destination, date, fields, row count, and digest. OMH uploads nothing, keeps
no raw value, and leaves the lawful basis to legal-compliance-review. Chat
routing to it is deliberately conservative: the words it lives on (redact,
PII, pseudonymize, strip, export, vendor) also name code, Hermes settings,
legal questions, issue triage, messages and posts, so it takes nothing
another skill holds. It has no routing boost, no other skill's guard stands
down for it, and it is scored only when a sentence leads with redact,
pseudonymize, anonymize, or de-identify on a file leaving the team, such as
"de-identify this export for the researcher". Logs for a GitHub issue, a
transcript excerpt, or a dataset for a contractor stay with the skill that
holds them, while Hermes' own skill index, or naming the skill, can still
select it.
-
The coding lane works with Hermes' own delegation, board, and debugging
skills instead of beside them. ulw-work loads a Hermes-only
native-delegation reference before a delegate_task dispatch. Each lane it
writes itself carries an output_schema holding only the fields integration
reads; the host's schema_valid is read only from a result returned in the
same turn, a later completion message is checked against the schema by hand,
completed is never read as validated, and a lane's answer stays its own
report until the verification fan-in runs. With the user's
delegation.worktree_isolation on, each lane works on its own
hermes-subagent/… branch, so integration is a merge the parent performs
before any check, after committing whatever a lane left uncommitted in its
worktree: the checked team lane now says a check run before that
merge tests a tree without the lane's work, and the file-ownership manifest
is compared per lane branch. A one-shot run, which is also how a kanban
worker runs, that is refused for its delegation budget finishes the
remaining lanes inline in dependency order instead of retrying. The kanban
lane recipe adds completion_contract (the board refuses completion until
the repository's required checks pass on the PR's current head, a record the
closing brief still checks against the PR head), goal_mode with
goal_max_turns, kanban_request_review into the review column, and
kanban_schedule where the worker has it; omh_agent_board now admits the
two goal fields on a create and reads back a card in the host's scheduled
status instead of failing the receipt. agent-instructions documents how
Hermes loads context files: one file type per session, .hermes.md first,
every AGENTS.md from the repository root down, and a per-directory
AGENTS.override.md the inventory has to list. plan treats a file saved
by Hermes' built-in /plan as its draft after that turn, with pasted code
reduced by the proportion check and acceptance still taken only from the
user. On Hermes, decision-prototype keeps its decision record when the
bundled spike builds the experiment, app-debugging writes its records at
each phase of the bundled systematic-debugging and counts a
python-debugpy or node-inspect-debugger read as one observation, and
ask takes only the invocation from the bundled claude-code, codex, or
opencode skill for a CLI advisor the user named, with no CLI as the
default.
-
Generated skills follow more of Hermes' own skill-authoring
conventions. Every Hermes skill body now opens its trigger section with
## When to Use, the heading Hermes' skill linter looks for, and carries
license: MIT and author in its frontmatter (the Agent Skills projection
carries license only, the field that spec defines). Pointers to the
references the router skill owns (the shared rail, the Jev rail,
structural code search, workflow artifacts) are written as the call that
loads them, such as
skill_view(name='omh-routing', file_path='references/skill-common-rail.md'),
instead of a bare path the model had to translate. A test now holds every
shipped SKILL.md free of Hermes' inline-shell shape, which Hermes would
run as a command when skills.inline_shell is on.
-
Three request shapes that belong to a skill Hermes bundles, or to a
work board, stop dispatching an OMH skill. An architecture diagram of
cloud or infrastructure pieces described in words, with no codebase,
repository, module, folder, src tree, CDK or Terraform named, no longer
dispatches codebase-uml; Hermes bundles architecture-diagram for it.
An English message naming an LLM wiki no longer reaches the wiki
blueprint, nor the research department unless one is named outright;
Hermes bundles llm-wiki. A review of what sits on a kanban, board, task,
Trello or Jira card no longer opens an image card; a dashboard, scoreboard
or storyboard card still does. Each of those turns now asks instead.
Measured on the chat-interaction surface over both routing corpora, every
sentence literal in the routing tests, the sentences this change was
probed with, and its reviews' sentences: those are the only routes whose
action or selected skill moves, each from a dispatch to a clarify. arXiv
lookups, citation checks and paper research route as they did. The
research-department body maps Scout to the research and web-research
lanes its prepared plan emits, and handoff policies, like Do Not Use When
lines, name siblings by the labels skill_view loads.
-
Skill bodies name their siblings by the name Hermes can load, and say
which requests belong to a skill Hermes bundles. A ## Do Not Use When
line that hands a request to a sibling used to name it by its catalog name
(connector-operator, strategy-brief, research), which skill_view
cannot load because the installed directory carries the display label
(omh-apps, omh-decide, ulw-research). The renderer now writes the
label in both the Hermes body and the Agent Skills projection; the catalog
keeps canonical names, so routing and the deference graph are unchanged. A
sibling that is no longer installed keeps its catalog name. The Hermes
frontmatter gains metadata.hermes.related_skills, derived from those same
lines, which skill_view returns beside the body; Hermes' per-turn skill
index does not read it, and the index size is unchanged. A skill whose job
overlaps a skill Hermes bundles now carries one line naming which request
belongs to the bundled one: requesting-code-review, systematic-debugging,
simplify-code, spike, dogfood, llm-wiki, grounded-citations,
arxiv, architecture-diagram, github, claude-code / codex /
opencode, sdlc-review, meeting-action-items, humanizer, pdf /
docx / powerpoint / xlsx, hermes-agent-skill-authoring, and
competitor-news-monitor. Those lines are Hermes-only, no other host
bundles those skills: the deferral lines web-research,
research-department, visual-qa, ultraqa and code-review already
carried for grounded-citations, arxiv, competitor-news-monitor,
dogfood and sdlc-review keep their wording and now leave the Agent
Skills projection too, each counterpart named once per skill.
-
The memory and learning skills now read what Hermes' own learning loop
wrote or is holding: pending memory writes, staged skill writes, the skill
audit ledger, curator run reports, and the one memory-provider slot.
memory-sync lists the memory writes Hermes holds for approval under
pending/memory/ as proposals the person decides with /memory approve or
/memory reject, reports a native write that comes back staged: true as
waiting rather than saved, and reads each file's cap from the inventory,
with the fallback figures taken from the plugin bundle's own Hermes memory
reader rather than a second copy. Hermes' write_approval is described
as Hermes' gate on Hermes' own writes: a safe omh_memory capture is still
approved by OMH's auto-safe policy with no person in the loop, OMH never
approves or rejects a pending write, and it never proposes turning the gate
on.
external-connector-readiness states that Hermes runs one external memory
provider, so adopting another provider where memory.provider reads omh
stops OMH's per-turn recall and dreaming reminders and leaves omh_memory
refusing to recall or write records; the switch stays a proposed diff the
user applies. It also records the plugin install scan and the OSV malware
check for npx, uvx, and pipx MCP servers only from output that was
seen, since a quiet install or launch is not a clean result.
workflow-learning reads the skill audit ledger and reports agent or
background-review skill writes that no store route accounts for as
unreviewed_native_write (no OMH record of the write, not proof nobody
reviewed it), and counts an approved update as landed from the ledger only
when an agent or user entry creates, edits, patches, or writes the
approved file after the approval;
instinct-ledger keeps such a write out of an instinct's evidence and
promotes through store routes; rules-distill lands an approved candidate
in the user's own Hermes skills through skill_manage, never an OMH-managed
skill, and reads curator run reports as one observation each.
skill-health reads the ledger for managed skills changed outside OMH,
lint_warnings from skill writes, and hermes skills check for hub
updates, and never presents use or load counts as a reason to prune,
archive, or retire a skill. skill-scout fills its candidates from
hermes skills search and inspect with each source's trust level, and a
scan verdict only from install or audit output. prompt-import-readiness
starts from the hermes import-agent --dry-run preview, which skips Claude
Code's slash-command prompts and does not read Codex prompt files, makes a
skill the conversion target, and checks names against built-in commands,
quick commands, plugin commands, skill bundles, and skills in the CLI's
order. The seven feature-surface skills among these state their own Why
and Do-Not-Use.
-
The run-efficiency report now carries what Hermes itself recorded for a
named session, and the tracker skills point at Hermes' own usage, compaction,
tool, agent, stop, and skill surfaces. omh runtime efficiency-report --hermes-session <id> adds a host_usage section from the part of the cost
receipt omh_run_summary returns that Hermes itself accounts for in
state.db (the session, its delegated children, and its kanban workers;
executor-reported fanout units are left out), read-only: observed only when
that usage recorded tokens, with each amount's basis kept beside it (a
Hermes estimate is not a charge), while a session Hermes has no row for, one
with no recorded tokens, or a Hermes home whose state.db is missing or
unreadable stays not_observed with that reason instead of reading as
zero, and provider billing stays not_observed either way. The cost
receipt now names which of its reads hit a bound (truncated_sources).
run-efficiency, ops-observability-card, and context-budget-review
answer "what has this conversation used or cost" by what each Hermes
surface shows: /usage this session's tokens and context, /insights an
estimated cost across recent sessions, and omh_run_summary this
conversation's recorded tokens and cost; context-budget-review stops
sending the question to the ops card, which cannot answer it.
context-budget-review turns its summarization checkpoint into a
/compress <focus> the person runs, offers --preview only in the classic
CLI or on a messaging platform and never when the surface is unknown,
because a modern TUI that does not parse the flag compresses for real, and
counts a preview only from Hermes' own "no changes made" reply. toolbelt-readiness counts a tool deferred behind
tool_search as present, never missing. running-work-board adds this
conversation's Hermes delegate children and kanban workers from omh_hud.
cancel clears OMH state with OMH's own commands and hands host work to the
person's own Hermes stop commands (/stop, /loop stop, /goal pause or
/goal clear, /heartbeat clear, /pause), never ending a host process
itself, and reports a host stop as requested until Hermes answers. skill
lists, reads, and edits the person's skills with Hermes' skills_list,
skill_view, and skill_manage, leaves search, install, and hiding to the
person's hermes skills commands, and never edits an OMH-managed skill in
place. capability-toggle sends hiding one skill on one platform to Hermes'
own hermes skills config.
-
Hermes' background review and /btw side question no longer use up the
once-per-session OMH lines meant for the person's next turn. On Hermes
0.21.1, the plugin's floor, both run as a fork of the live agent that keeps
the session's id and names that same id as its parent, and the fork's turn
still ran OMH's pre_llm_call. A review runs right after a turn, so it took
the board card naming this chat's open lanes, counted toward the plan line's
turns with the full reconciliation rule, and replaced the session's last
route-hint and skill-candidate claims; a side question asked mid-turn
cleared that turn's Jev marker, so an omh_jev_ask the person had asked for
returned consent_not_observed. The fork was handed OMH context of its own
as well: with Hermes' review prompts, the primer, a route hint, the
candidate line, the plan line, and the board card. pre_llm_call now
returns nothing for a turn whose parent_session_id equals its
session_id, before it reads or records anything, which is what Hermes
0.21.2 and later do by not calling the hook for such a fork. A delegate
child, which names its parent's id, and a turn that names no parent are
unchanged. The held-write line's own fork check moves to that one place.
Other hooks a fork reaches are unchanged.