Repository navigation
Conversation
|
@Dawncoral is attempting to deploy a commit to the Roo Code Team on Vercel. A member of the Team first needs to authorize it. |
This branch has not been 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.
What
Adds one concrete, tested configuration example (Kimi K3.1 Pro via Wallaby) to the OpenAI Compatible provider page: base URL, model ID, and the exact Context Window / Max Output values Roo Code asks for.
Why
The page covers the general settings and native tool calling requirement, but has no worked third-party example. The model ID and the two numeric model-configuration fields are where users most often guess wrong; this entry fills them in and links a machine-readable rate card.
Disclosure
I run Wallaby. Kept the entry factual (settings, pricing link, status page), appended it at the end without touching existing text, and matched the page's format. Happy to trim or relocate if you prefer a different place for it.