Repository navigation
📋 docs: Managing user-provided API keys with Model Specs - #630
Closed
danny-avila wants to merge 1 commit into
Closed
danny-avila wants to merge 1 commit into
danny-avila wants to merge 1 commit into
Conversation
Document that user-provided endpoint keys can be set or rotated from Settings → Data controls → API keys even when Model Specs hide `modelSelect`, and that the list is scoped to reachable endpoints (spec endpoints + `addedEndpoints`, expanding to agent `allowedProviders` when agents is reachable). Also lists `agents` as a valid `addedEndpoints` value. Companion docs for LibreChat #13864.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📦 Next.js Bundle Analysis for librechat.aiThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
Collaborator
|
Thanks for this, @danny-avila! This is now covered by #666, which adds the "Managing user-provided API keys with Model Specs" callout to |
This branch was successfully deployed
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
Documents how end users manage user-provided API keys when Model Specs are configured, matching the new Settings behavior added in LibreChat PR LibreChat-AI/LibreChat#13864.
Edits
content/docs/configuration/librechat_yaml/object_structure/model_specs.mdx:Calloutright where the docs explain that Model Specs hidemodelSelect. It clarifies that users can still set/rotate keys forapiKey: "user_provided"endpoints from Settings → Data controls → API keys, and that this list is scoped to the endpoints a user can actually reach — the specs' endpoints plusaddedEndpoints, expanding to the agentallowedProviderswhen theagentsendpoint is reachable.agentsto the documented set of validaddedEndpointsvalues (it is schema-valid and is referenced by the new behavior).Why
Before, when
modelSpecs.listwas set,interface.modelSelectdefaulted tofalse, hiding the endpoints dropdown and the gear icon that opened the Set API Key dialog — leaving no way to enter or rotate auser_providedkey. The companion code PR surfaces that flow in Settings and scopes it like the model selector / mention popover; these docs explain it.Notes
prettier --checkpasses on the edited file; internal anchors (#addedendpoints,agents#allowedproviders) resolve to existing headings.