[Docs] Document OpenCode Go model limits - #51
Draft
zoomote[bot] wants to merge 1 commit 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
Added an OpenCode Go provider guide covering API-key setup, dynamic model discovery, and Zoo Code's model-limit fallback behavior. The provider is also registered in the documentation navigation.
Why this change was made
Zoo Code now maintains explicit limits when OpenCode Go returns model IDs without metadata, and users need a provider-specific reference for that behavior.
Impact
Users can find OpenCode Go in the provider docs and understand why context limits remain accurate even when the upstream model-list response omits them.
Related PRs
Screenshots