8d8836ddb1
Five opt-in counters that tune the agent loop itself, recorded through record_process_mark (disabled config => zero rows, zero files): - hermes.file_edit.count: tool, mode, outcome, match_strategy. The fuzzy matcher reports the strategy that landed (or no_match / ambiguous) into a context-local probe opened only around the patch/write_file handlers, so we learn which strategies earn their keep without counting internal callers. - hermes.loop_guard.count: provider, model, signal, detector. Hooked where the guardrail already warns/blocks/halts and at turn end for the iteration budget; latched once per turn per (signal, detector). - hermes.tool_recovery.count: provider, model, tool, next_tool, next_outcome. One row per failed tool call, resolved against the model's next round (same tool first) or the turn end (no_tool_call / gave_up). - hermes.terminal.outcome.count: backend, command_kind, outcome. The kind is a table lookup on the first program word, never the text. Hermes' own deadline/interrupt now set hermes_timed_out / hermes_interrupted on the backend result, so a command's own `exit 124` reads nonzero, not timeout. Disjoint dims from hermes.execution_backend.count (served vs not). - hermes.model_reply_issue.count: provider, model, issue. Refusal and truncation only from the structured finish reason; empty/reasoning_only from the normalized message; issue=none per response as the denominator (model_route counts attempts and files empty replies as failures). Background review / curator loops and _host_local / unmetered terminal calls never count. Helpers live in shared_metrics_harness.py; call sites are one or two lines each.
Website
This website is built using Docusaurus, a modern static website generator.
Reading the docs on GitHub? The Markdown under
docs/is authored for the rendered site at https://hermes-agent.nousresearch.com/docs/. Cross-page links are relative Markdown paths, so they follow through on GitHub's file viewer too. Every page on the site has an Edit this page link that opens the source file here.
Authoring links in docs/
- Link to another page with a relative Markdown path, anchors included:
[Profiles](../user-guide/profiles.md),[Bundles](../user-guide/features/skills.md#skill-bundles). Docusaurus turns the file path into the page route; GitHub follows the same path. Site routes (/user-guide/profiles,/docs/user-guide/profiles) only work on the rendered site — GitHub resolves them as repository paths and 404s, and the/docs/form also emits/docs/zh-Hans/docs/...404s in the zh-Hans build becausebaseUrlis already/docs/. python3 website/scripts/check_doc_links.pyfails on any route-style link in hand-authored pages (EN and the zh-Hans mirror);--fixrewrites them. It runs in theDocs Site Checksworkflow. Generated pages (user-guide/skills/{bundled,optional},reference/*skills-catalog.md) are produced byscripts/generate-skill-docs.py, which emits the same relative form.- Pin
{#anchor}on cross-linked headings so the zh-Hans mirror keeps the same id.
Installation
yarn
Local Development
yarn start
This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
Build
yarn build
This command generates static content into the build directory and can be served using any static contents hosting service.
Deployment
Using SSH:
USE_SSH=true yarn deploy
Not using SSH:
GIT_USER=<Your GitHub username> yarn deploy
If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the gh-pages branch.
Diagram Linting
CI runs ascii-guard to lint docs for ASCII box diagrams. Use Mermaid (````mermaid`) or plain lists/tables instead of ASCII boxes to avoid CI failures.