fc4dbe32df
`hermes logs --since` and `--level` passed every line that had no leading timestamp. A traceback's frames are written without one, so an old error printed its frames without the header that was filtered out, and `--component` dropped the frames of a matching record. `hermes logs` now reads each unstamped line as part of the record above it: the line gets that record's verdict for every filter, in the tail read and in `-f`. Lines before the first stamp in the read window have an unknown time and level, so they are dropped when `--since` or `--level` is set. mcp-stderr.log had no parseable stamp at all: the banner started with `=====` and server output was copied raw, so `hermes logs mcp --since` printed the whole file. The stderr tee already reads each server's stderr in a thread, so it now writes one line at a time, each prefixed with the asctime-shaped local stamp the Python logs use. The banner starts with the same stamp. The stamp comes from new public `timestamp()`/`stamp_line()` in hermes_cli/stderr_timestamp.py, which stays stdlib-only. The desktop MCP log view accepts both banner shapes. A test now requires a real writer's sample line for every LOG_FILES entry to parse with `_parse_line_timestamp`. The docs no longer say the `timezone` key changes log timestamps; log lines use the machine's local time.
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.