e00aa13d7d
A member's hidden per-group session is an ordinary Hermes session, so the CLI (`hermes -p <bot> chat --resume "Group: <room> · <thread>"`), cron and the agent's own tools append to it too. Those rows reached the transcript but never the room log, so the room silently diverged from what the member actually said. What: new sibling group-external-writes.ts sweeps each member session's unseen tail on the two paths that already read it — the pre-resume snapshot in runGroupChatMemberTurnLeased and the stranded-marker harvest — and appends the rows the room engine did not write itself, authored by that member, in the session key's thread. Cursor keyed by the SESSION key (`thread:<t>::<memberKey>`) in room.externalCursors, persisted through all three room projections (updateGroupChat, durableGroupChatRooms, plugin.tsx hydrate) so a window restart never re-mirrors a row. Why the classifier is header-based: every room-fed prompt opens with the header buildGroupChatTurnPrompt writes (now the exported GROUP_PROMPT_HEADER_PREFIX), agent-injected `[System:` rows continue the open exchange, and an assistant row answers whichever user row preceded it. Why the round watermark walk: mirrored rows land after the round's submit anchor, so `anchorIdx + 1` re-fed the member its own CLI conversation as room news and drove an extra turn. A member's own entries are never news to their author; the walk generalises the existing tail bump for replies. Why the `at` stamps: the gateway mirror merge orders same-millisecond entries by id, so a burst of mirrored rows appended in one tick came back shuffled. Ports the types.ts/group-chat.ts externalCursors persistence hunks of PR #94340; its memberKey cursor and 'legacy' thread predate per-thread member sessions and are replaced by the session-key cursor. Co-authored-by: YusukeOshima-5564 <yusuke_oshima@capsor.co.jp>
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.