All plugins

htmi

Review the HTML pages your agent writes, on the page itself: comment on the exact element, chart, table row or passage; Hermes is told about new comments, reads each one with its context, makes checked edits and replies. Pages can also be published as a GitHub issue or pull request description, and comments posted there are pulled back. Adds 11 tools, a pre_llm_call notice, a pre_tool_call approval gate, a skill, the /htmi command and a Review tab in the dashboard. Disclosure — runs its bundled engine (bundle/htmi.mjs, built from the repo's src/) with Node and runs git and gh with a minimal environment that carries no provider keys; reads and edits documents only inside the current repository (comments go to .htmi/); opening a review page starts a local review server on 127.0.0.1 (token-protected writes) that keeps running in the background until /htmi stop or a restart; GitHub work uses your own gh CLI login and only this repository's origin plus repositories you list in github_repos: creating an issue or replacing or editing a description waits for your approval, and replies to comments that came from GitHub are posted there; no telemetry, no stored credentials, no other third-party services.

Thamirawaran1Toolsv0.1.1Updated 7 days ago

About

Review the HTML pages your agent writes, on the page itself: comment on the exact element, chart, table row or passage; Hermes is told about new comments, reads each one with its context, makes checked edits and replies. Pages can also be published as a GitHub issue or pull request description, and comments posted there are pulled back. Adds 11 tools, a pre_llm_call notice, a pre_tool_call approval gate, a skill, the /htmi command and a Review tab in the dashboard. Disclosure — runs its bundled engine (bundle/htmi.mjs, built from the repo's src/) with Node and runs git and gh with a minimal environment that carries no provider keys; reads and edits documents only inside the current repository (comments go to .htmi/); opening a review page starts a local review server on 127.0.0.1 (token-protected writes) that keeps running in the background until /htmi stop or a restart; GitHub work uses your own gh CLI login and only this repository's origin plus repositories you list in github_repos: creating an issue or replacing or editing a description waits for your approval, and replies to comments that came from GitHub are posted there; no telemetry, no stored credentials, no other third-party services.

HTMi for Hermes Agent

Review rich documents with Hermes the way you review code: on the page itself.

Agents write more and more of their work as documents: plans, designs, comparisons,
reports as HTML pages, Markdown with Mermaid diagrams, long issue and pull request
descriptions. Reviewing them in chat is clumsy. You describe where something is ("the
second table, the risk about failover"), the agent guesses, and after an edit nobody
knows which comments still apply.

With HTMi you read the document as authored and comment on the exact element, passage,
diagram part or image region. Each comment is pinned to its target and to the version
you saw. Hermes is told about new comments at the start of its next turn, reads one with
exactly the context it needs, changes the source through checked edits, and replies. A
comment survives the edit, or says plainly that its target changed or is gone.

What it adds to Hermes

Toolshtmi_list_documents, htmi_read_document, htmi_list_targets, htmi_list_comments, htmi_comment_context, htmi_apply_edit, htmi_reply, htmi_validate, htmi_pull_comments, htmi_publish_description, htmi_open_review
Hookpre_llm_call: when people left new review comments since the last turn, Hermes gets a short notice naming them (id, document, target, author). The comment text is not put into the prompt; Hermes reads a comment with htmi_comment_context when it acts on it.
Hookpre_tool_call: before HTMi creates an issue, replaces a description or edits one on GitHub, Hermes asks you to approve, naming the repository and the change; a repository outside the allowed ones is refused.
Command/htmi open [document], /htmi comments, /htmi stop, /htmi init, /htmi status
Skillhtmi:document-review: how to write a document for review and act on comments
Dashboarda Review tab in hermes dashboard that shows the running review pages in place

Use

  1. Install and enable the plugin, then start Hermes in a git repository:

    hermes plugins install Thamirawaran/htmi/hermes --enable
    hermes gateway restart   # only if a gateway is already running, so it loads the plugin
    
  2. Ask for a document, for example "write the cache plan as an HTML page I can review".
    Hermes writes it, checks it with htmi_validate and opens the review page.

  3. Open the address it gives you (or run /htmi open docs/plan.html). Click an element,
    select a passage or draw a region on an image, and write your comment.

  4. Back in Hermes, say "go through my comments". Hermes reads each one with its context,
    answers questions, edits what you asked for, and replies on the comment. You resolve
    comments; Hermes cannot.

Comments live in .htmi/annotations.jsonl in your repository, next to the documents,
so they travel with the repository through git.

To see pages and comment on GitHub, add the HTMi Chrome extension: download
htmi-chrome-0.1.0.zip from the
latest release, unzip it, and in
chrome://extensions turn on Developer mode and choose Load unpacked.

Remove the plugin with hermes plugins remove htmi. Your documents and .htmi/ stay.

Requirements

  • Hermes Agent 0.23.0 or newer.
  • Node.js 20.11 or newer. Hermes installs one; HTMi uses it, or else the node on your PATH.
  • git. GitHub descriptions (github:owner/repo#7) also need the GitHub CLI gh, signed in.

What it does on your computer

Hermes asks plugins to say this plainly.

  • Shell commands. Every tool runs node bundle/htmi.mjs <command> in the session's
    repository. The engine runs git to read revisions, and gh only for GitHub issue or
    pull request descriptions. The plugin also runs git rev-parse to find the repository
    and git remote get-url origin to find its GitHub repository. None of these see
    Hermes's own environment: they get an explicit minimal one (PATH, HOME, locale,
    temporary folders, the XDG folders, proxy and certificate settings, and the GH_*,
    GITHUB_TOKEN and GIT_* variables gh and git use), so provider keys never reach
    them.
  • Files outside the plugin. HTMi reads documents in the session's repository and the
    files they use (stylesheets, images), and nothing outside it: a path that leaves the
    repository, also through a symbolic link, is refused for reading and for writing. It
    writes .htmi/annotations.jsonl when comments or replies are added, .htmi/config.json
    and .gitattributes on /htmi init, and a document when htmi_apply_edit changes it
    (only the named part; the edit is refused if anything else would change).
  • A background process. htmi_open_review and /htmi open start htmi serve for the
    repository: a web server on 127.0.0.1 only, on a port the system picks. It keeps running
    so you can keep commenting while Hermes works, until /htmi stop or a restart. Its
    address and process id are kept in the plugin's data folder. Only local pages (the
    dashboard's Review tab) may show it in a frame.
  • Network. HTMi reaches GitHub only for GitHub descriptions, always through your own
    gh login: htmi_publish_description creates an issue or sets a description,
    htmi_pull_comments reads its comments, htmi_reply posts a reply to a comment that came
    from there, and reading or editing a description reads and writes that description.
    Nothing else leaves your computer.
  • Which repositories, and your approval. HTMi works on GitHub only in the repository's
    own origin remote and the repositories you list in the plugin's github_repos setting
    (plugins.entries.htmi.settings.github_repos in config.yaml, or the plugin's settings
    in the Desktop app). A repository the model names, or one set in the repository's
    .htmi/config.json, is not enough. Creating an issue, replacing a description and
    editing a description each wait for your approval in Hermes, with a message naming the
    repository and what changes. In a run with nobody to ask (hermes chat -q, cron), they
    are refused unless you set Hermes to approve in that mode (approvals.single_query_mode,
    approvals.cron_mode).
  • Credentials and telemetry. None stored, none sent. The review page uses a random
    token held in memory to accept comments from its own page only.

Inside

The engine is HTMi itself, bundled into bundle/htmi.mjs: one unminified ES module built
from src/ of the HTMi repository by
npm run bundle:engine. A test in that repository fails if the bundle differs from what
the source builds. The Python files translate between Hermes and the engine, and
policy.py holds the GitHub rules above.

Tests: uv run --no-project --with pytest pytest hermes/tests from the repository root.
They run the real engine in a temporary git repository; where a test must see what gh
would receive, a small probe program stands in for gh and records its environment.

License

MIT, see LICENSE.

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

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section