[Docs] Document NanoGPT provider setup - #38
Draft
zoomote[bot] wants to merge 2 commits into
Draft
Conversation
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
1 participant
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.
What changed
Adds NanoGPT to the provider directory and documents API-key setup, model selection, routing preferences, catalog metadata, and the Muse Spark 1.2 Contributor compatibility behavior.
Why this change was made
Zoo Code has a dedicated NanoGPT integration, but the documentation site did not have a corresponding provider guide. The new page also explains the reliability behavior paired with the Muse Spark tool-call fix.
Impact
Users now have a discoverable setup reference for NanoGPT and can understand how Zoo Code keeps Muse Spark 1.2 Contributor's multi-turn tool-result context contiguous without disabling parallel calls.
Related PRs
Screenshots