2f1fabd4bf
* MEDIA: tags parsed once, in the backend; clients get clean text plus attachments tui_gateway runs the gateway's extract_media on the live stream (a tag's line is held until it completes, then the file goes out on that delta), on message.interim/message.complete, and on history through the shared history projection (session.resume and the REST messages route). The wire contract gets an attachments list on message.delta/interim/complete, TranscriptMessage and InflightTurn. Desktop renders attachments as data parts (media player or file card, HTML included) and in group rooms; the TUI lists them as link rows. The three renderer MEDIA: parsers (chat parts, speech text, Artifacts) and the TUI MEDIA line parser are deleted. Stored rows keep their raw tags. * Delete the ::preview directive and its prompt text The inline HTML widget, its registration and its hidden-turn talk-back go; an HTML file delivered with MEDIA: is a normal file card with preview. The desktop and TUI platform hints now describe attachments. The transcript.directives area stays for ::onboarding and ::ask. * MEDIA stream splitter works per line; group mirrors and sync keep files; TUI shows a file row when its line completes - MediaStreamSplitter splits each completed line once, carrying code-fence state, so prose that says "media:", blank-line runs and [[audio_as_voice]] no longer stall the stream, and cost stays linear in reply length. - The partial-tag hold applies only at a token start (or to an upper-case prefix), so words like "stream" are not held. - Subagent child mirrors stream through a splitter too, flushed at tool and end. - Group rooms: externally written rows and the ui_meta sync copy carry attachments; the echo guard compares files as well as text. - TUI: a delta that brings a new file seals the text so far with its file row.
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.