docs: tool provider selection follows the hermes tools pick (post #90317) - #90352
Merged
Merged
Conversation
Contributor
૮ >ﻌ< ა ci reviewran on 01d4c1d — docs: tool provider selection follows the hermes tools pick
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Docs now describe the strict provider-selection contract that merged in #90317: the provider picked in
hermes tools(or the desktop GUI) is what runs — one selection key per category,nous= managed Tool Gateway, vendor name = BYOK direct, credential presence never selects or reroutes, and a selected-but-broken provider errors by name instead of silently falling back.Follow-up docs PR for #90317 (the code merged before the docs check; per the new standing rule, future PRs carry their docs in the same diff — this is the catch-up).
Changes
user-guide/features/tool-gateway.md(+ zh): the per-tooluse_gatewaysection replaced with the one-key-per-category contract, exact error string, and a "Legacyuse_gateway(deprecated)" note covering read-time interpretation of old configsintegrations/nous-portal.md,guides/run-hermes-with-nous-portal.md: config examples rewritten fromuse_gateway: trueblocks toprovider/backend/cloud_provider: noususer-guide/features/image-generation.md(+ zh): strict routing + theFAL_KEYerror documenteduser-guide/features/browser.md(+ zh): Camofox is acloud_provider: camofoxselection;CAMOFOX_URLis address-onlyuser-guide/features/tts.md: explicit selection vs never-configured autodetect for TTS/STT;nousvalue documented; explicitstt.provider: localhonoreduser-guide/messaging/whatsapp-cloud.md: STT gateway setup nowstt.provider: nousreference/environment-variables.md(+ zh):CAMOFOX_URLmarked address-only13 files, 86 insertions / 64 deletions. No new pages, no sidebar changes.
Validation
npx docusaurus build(npm@12 ci)Infographic
Omitted: docs-only follow-up; image account on this box is the exhausted direct FAL key. Backfill via
gh pr editif wanted.