e56ec8c9f7
NAS maps the agent-cron bearer to a provisioned instance via an `agent:*` client or the `hermes-cli-vps` bootstrap session (hermes-portal `server/agent-cron/instance-auth.ts`). A container whose auth.json holds a plain `hermes-cli` user login is refused with 403 invalid_client on every arm, re-arm and list, for the life of that credential - and the re-login users try first (`hermes auth logout nous` + device code) replaces the bootstrap session, making it permanent. Chronos previously logged one bare warning per job and left the jobs with no trigger at all: they only ran through the misfire sweep, minutes late. NasCronClientError now carries the HTTP status and the OAuth `error` code. On an identity rejection the provider logs ONE warning that names the real remedy (restore the hosted credential from the Nous Portal; re-login cannot fix it), stops calling NAS, and starts the built-in ticker with the gateway's own adapters/loop so scheduled jobs keep firing on time. Transient 5xx/transport failures keep retrying on the next reconcile. Supersedes #97566 (@wesleysimplicio), whose runtime-credential swap resolves to the same bearer on main (`agent_key` is the access token) and so could not change the 403.
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.