[Docs] Explain OpenAI-compatible custom request fields - #46
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
The OpenAI-compatible provider guide now documents the Extra Body setting, includes a Sail Research
metadata.completion_windowexample, explains protected fields and profile-export security, and shows the new VS Code settings control.Why this change was made
Users need a concrete, provider-focused example for configuring custom request-body fields without relying on a proxy or mistaking them for HTTP headers.
Impact
OpenAI-compatible provider users can follow a complete setup example for custom request metadata and understand the validation and security boundaries before saving a profile.
Related PRs