37daf85b2a
Review findings on the assignee-login gate (#122689): - MAJOR: served_profile_child_env(inherit_credentials=True) overlays only the assignee's own GH_TOKEN/GH_CONFIG_DIR but HOME/XDG_CONFIG_HOME stay the launch process's, so a profile with no login of its own fell through to ~/.config/gh/hosts.yml - the ambient login the gate promises never to use. For a routed assignee home with neither token nor config dir, pin GH_CONFIG_DIR to <profile_home>/gh; gh then exits 4 (authentication required), which _api classifies as auth naming the profile. - MINOR (a): an ASSIGNED card whose profile cannot be resolved was fail-open (env=None -> completing process's full ambient login). Resolution now happens inside collect_acceptance and raises _GateAuthError naming the profile; only genuinely unassigned cards keep the ambient path. - MINOR (c): Codex refresh 200/non-JSON body no longer sets relogin_required, so the new exit-78 startup gate cannot turn an edge misfire into a sticky terminal block (invalid_json_relogin=False, as xAI already does). - MINOR (b)+(d) docs: GH_TOKEN must live in the profile's .env/secret source (a shell/systemd export is scrubbed); skipped_nonspawnable {assignee} row in the worker telemetry table; startup relogin-required failure exits 78.
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.