ec1238fa65
Independent review of the plugin refresh branch (#116553) found four gaps between what model-provider-plugin.md promises for `refresh_credential` and what `_refresh_entry_impl` did: 1. `replace(entry, **hook_result)` raised TypeError on any non-field key (`expires_in`, `token_type`, `scope` — the natural token-endpoint shape), the except benched the row EXHAUSTED and the pair the server had already rotated was dropped: for single-use refresh tokens that is a lost login. Field keys now go through `replace()`, everything else merges into `entry.extra` (mirrors `from_dict`); `None` = no rotation, mark ok. 2. Plugin providers skipped the locked single-use path, so a gateway and a CLI could both POST the same refresh token (`refresh_token_reused`). Providers with a hook now take the `_auth_store_lock` path: re-read the pool store, adopt a peer's usable rotation and skip the hook, else call it and write through. Eligibility derives from `plugin_refresh_hook()`, not from extending the built-in name tuple. 3. A raising hook re-benched EXHAUSTED every cooldown forever at DEBUG. `AuthError(relogin_required=True)` (or a grant-dead OAuth code) is now terminal: the row goes DEAD with a WARNING naming `hermes auth add`. Any other exception stays a transient bench (negative test kept). 4. `from_dict`'s extra sweep round-tripped a stray row-level `provider` key back onto the row on `to_dict()`; it is bookkeeping, not metadata. New logic lives in `agent/credential_pool_plugin.py` — credential_pool.py is at the size cap; the facade only dispatches. Part of #116408
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.