All plugins

wait-ledger

Local ledger of the times Hermes stopped to wait for you (approval prompts, clarify questions, password prompts): /waits shows how many waits there were, how many were answered or left unanswered, and how long Hermes stood still in total, typically and at most, per kind of prompt, per platform or per day, for the last 24 hours, any number of hours or days, the latest session or everything recorded; /waits recent lists the newest waits (ten, or up to 100 with /waits recent 50). Disclosure — writes wait metadata (session id, platform, kind of prompt, how it ended, wait time; no prompt text, answer or session key) to plugin-data/wait-ledger/waits.jsonl, trimmed to 5,000 rows past 2 MB; observer only, cannot answer, delay or change a prompt; no network

olric3015Toolsv1.0.0Updated 1 month ago

About

Local ledger of the times Hermes stopped to wait for you (approval prompts, clarify questions, password prompts): /waits shows how many waits there were, how many were answered or left unanswered, and how long Hermes stood still in total, typically and at most, per kind of prompt, per platform or per day, for the last 24 hours, any number of hours or days, the latest session or everything recorded; /waits recent lists the newest waits (ten, or up to 100 with /waits recent 50). Disclosure — writes wait metadata (session id, platform, kind of prompt, how it ended, wait time; no prompt text, answer or session key) to plugin-data/wait-ledger/waits.jsonl, trimmed to 5,000 rows past 2 MB; observer only, cannot answer, delay or change a prompt; no network

wait-ledger

A local ledger of the times Hermes stopped and waited for you, and a /waits command that
shows how often it waits, on what, how those waits end and how long they take.

Hermes blocks on a person in three places: an approval prompt for a dangerous command, a
clarify question it asks you mid-task, and a password prompt for a command that needs one. While
it waits, the task stands still. wait-ledger subscribes to on_human_input_request and
on_human_input_resolved and keeps one row per wait, so you can see afterwards that a task
spent twenty minutes waiting on you today, that clarify questions on your phone mostly time
out, or that one kind of prompt holds things up far more than the others.

Install

hermes plugins install wait-ledger --enable

Requires Hermes 0.21.6 or newer (the release that added these hooks). No API key, no
configuration, no dependencies.

Use

/waits             last 24 hours, by kind of prompt (approval, clarify, sudo)
/waits session     the most recent session that waited
/waits all         everything in the ledger
/waits 7d          the last 7 days (any number of hours or days: 6h, 30d)
/waits platforms   add to any of the above to group by where it waited
/waits days        add to any of the above to group by day, newest first
/waits recent      add to any of the above to list the newest 10 waits instead
/waits recent 25   the newest 25 instead (1 to 100)
/waits clear       delete the ledger

Example (/waits all, from the end-to-end test: two approval prompts, three clarify questions
of which one timed out and one failed, and two password prompts of which one got an empty
answer; each answered a fraction of a second late on purpose):

Waits, all recorded:

kind      waits  answered  unanswered  total wait  median  longest
approval      2         2           0        0.8s    0.4s     0.5s
clarify       3         1           1        0.7s    0.2s     0.4s
sudo          2         1           0        0.5s    0.3s     0.3s
total         7         4           1        2.0s    0.3s     0.5s

Unanswered: timed out, withdrawn or never delivered. An empty answer or a failed prompt
counts in waits only.
  • kind is Hermes's own label for the prompt: approval, clarify or sudo (the password
    prompt). Grouped by platforms, the first column is where it waited instead (cli,
    telegram, ...).
  • waits counts prompts. answered is an approval you allowed or denied, a clarify
    question you answered, or a password you gave. unanswered is a prompt nobody answered: it
    timed out, the turn ended or was interrupted, or the message could not be delivered.
  • total wait, median and longest are how long Hermes stood still, from the prompt
    appearing to the wait ending, however it ended. The largest total wait comes first.

/waits recent lists the newest ten waits of the chosen window, newest first (/waits recent 25 lists 25, up to 100). From the same run:

Waits, all recorded, newest 7 of 7:

when        kind  platform      ended  wait
2s ago      sudo       cli    skipped  0.2s
2s ago      sudo       cli   provided  0.3s
2s ago   clarify       cli      error  0.1s
2s ago   clarify       cli  timed_out  0.2s
3s ago   clarify       cli  submitted  0.4s
3s ago  approval       cli       once  0.3s
4s ago  approval       cli       deny  0.5s

ended is how Hermes reported the end of the wait: an approval answer (once, session,
always, deny, timeout, ...), a clarify outcome (submitted, timed_out, undelivered),
a password prompt outcome (provided, skipped, timeout, cancelled), or error.

/waits days puts one day on each line, newest day first; days are your computer's local
calendar days. A time window counts back from now (/waits 6h, /waits 7d platforms,
/waits 30d days). The ledger keeps its newest 5,000 rows, so a long window on a busy install
reaches back only as far as those rows do.

What it does not see

  • Waits Hermes never has: an approval you already gave for the session or permanently,
    approvals.mode: off, yolo mode, and one-shot (-q) or cron runs, where nobody could answer.
  • Prompts that are not one of Hermes's human-input points (for example a smart-mode approval
    verdict, which is a model's answer, not yours).

What is recorded

One JSON line per wait in <HERMES_HOME>/plugin-data/wait-ledger/waits.jsonl (per profile):

ts, session_id, platform, kind, outcome, result, wait_s.

Not recorded: the prompt text (the command, the question), the session key (it can hold a
platform chat id), and what you answered. Your answers and passwords never reach the hooks at
all, and Hermes redacts the prompt text before handing it over; the plugin drops it anyway. Only
the prompt's random id and the time it opened are held in memory, until the wait ends.

The file is bounded: once it passes 2 MB it is rewritten to its newest 5,000 rows.

Security and footprint

  • register() only registers two hooks (on_human_input_request, on_human_input_resolved)
    and one command (/waits).
  • Observer only: it cannot answer, delay or change a prompt. Each hook call notes a time or
    appends one line to the ledger, and nothing else.
  • No network access, no subprocesses, no downloads, no credentials read.
  • Writes only waits.jsonl under its own plugin data directory. /waits clear deletes it.
  • The hooks never raise: if the ledger cannot be written, the failure is logged at debug level
    and the prompt is not affected.
  • Standard library only.

Development

python -m pytest tests                                            # unit tests, no Hermes needed
PYTHONPATH=<hermes checkout> python tests/e2e/wait_ledger_e2e.py   # Hermes's own prompts
hermes plugins validate wait-ledger

Changes

  • 1.0.0: first release.

MIT licensed.

README from the reviewed commit c44b60a; it updates when the author re-pins.

More by olric3015

18 plugins by olric3015 in the catalog.

olric3015approval-ledgerLocal ledger of Hermes's approval prompts (dangerous commands, protected writes, MCP consent, smart-mode verdicts): /approval-log shows how often each rule asked, how many prompts were approved, denied or left unanswered, and how long a person took to answer, per rule, per surface or per day, for the last 24 hours, any number of hours or days, the latest session or everything recorded; /approval-log recent lists the newest decisions (ten, or up to 100 with /approval-log recent 50). Disclosure — writes decision metadata (session id, surface, rule label, answer, timings; no command, description or session key) to plugin-data/approval-ledger/approvals.jsonl, trimmed to 5,000 rows past 2 MB; observer only, cannot answer or change an approval; no networkCommunitytoolsolric3015aux-ledgerLocal ledger of Hermes's auxiliary LLM calls (titling, compression, vision, approval): /aux shows tokens, time and failures per task, model, provider or day, or lists the newest calls (ten, or up to 100 with /aux recent 50), for the last 24 hours, any number of hours or days, the latest session or everything recorded. Disclosure — writes auxiliary-call metadata (ids, models, timings, token counts, no prompt or response text) to plugin-data/aux-ledger/calls.jsonl, trimmed to 5,000 rows past 2 MB; no networkCommunitytoolsolric3015b64-ref@b64: context references that decode encoded text for the model: @b64:<value> takes base64 (standard or URL-safe, padded or not), hex (0x48656c6c6f, 48:65:6c, \x48\x65), percent-encoding or a data: URI, told apart by the value's shape or picked with base64:, base64url:, hex: or url:, and attaches what it holds: text as text with control and invisible characters escaped, JSON pretty-printed, gzip and zlib inflated in memory (at most 1 MiB, one layer), and binary named by its format (PNG and GIF with their size, JPEG, PDF, ZIP, ELF, SQLite and more) with a hex dump of its first 128 bytes; notes point out a value that was cut short, padding that is off, a second layer of encoding and a JWT inside; the TUI and Desktop composer preview a value as you type it. Disclosure — reads only the text of the reference itself, using Python's base64, json, urllib.parse and zlib; nothing decoded is run, opened or saved; no network, no files read or written, no subprocess, no credentials read; the plugin keeps no copy of what it decodes, but the @b64: reference and the decoded contents become part of the message sent to your model provider and saved in the session history, so decode only values you are willing to share with it; register() only adds the @b64: reference provider.Communitytoolsolric3015chmod-ref@chmod: context references that explain a file permission mode for the model: @chmod:<mode> takes an octal mode (755, 0755, 4755), ls -l text (-rwsr-xr-x, with the file type letter and a trailing + . or @) or an st_mode as stat and git write it (100644), and attaches both forms, each class's rights in words (directory rights named as such), what setuid, setgid and the sticky bit do and where they are ignored, and notes such as a mode everyone can change, one private to the owner, or a class holding rights the class before it lacks; @chmod:"644 u+x,go-w" applies a symbolic change step by step the way GNU chmod does (u g o a, + - =, r w x X s t, copies like u=g), @chmod:"100644 100755" shows what changes between two modes, and @chmod:"umask 027" shows what new files and directories get; the TUI and Desktop composer preview a mode as you type it. Disclosure — reads only the text of the reference itself, using Python's re; it never looks at a file on disk; no network, no files read or written, no permission changed, no subprocess, no credentials read; the plugin keeps no copy of what you write, but the @chmod: reference and the explanation become part of the message sent to your model provider and saved in the session history; register() only adds the @chmod: reference provider.Communitytools

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section