[Feat] Add custom request fields for OpenAI-compatible providers - #1350
Open
zoomote[bot] wants to merge 8 commits into
Open
[Feat] Add custom request fields for OpenAI-compatible providers#1350zoomote[bot] wants to merge 8 commits into
zoomote[bot] wants to merge 8 commits into
Conversation
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
edelauna
marked this pull request as ready for review
August 28, 2026 01:11
edelauna
requested review from
JamesRobert20,
edelauna,
hannesrudolph,
navedmerchant and
taltas
as code owners
August 28, 2026 01:11
edelauna
force-pushed
the
roomote/openai-extra-body-visual-baseline
branch
from
August 28, 2026 01:11
97e9415 to
5bf75a2
Compare
github-actions
Bot
added
awaiting-review
Contributor
Review processThis PR was opened by an automated account. A human maintainer must verify the change intent, provenance, and validation before merging.
Current step: Resolve the merge conflicts. The review sequence resumes after the branch is mergeable. |
github-actions
Bot
added
awaiting-review
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
2 participants
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
OpenAI-compatible provider profiles now include a localized Extra Body JSON editor for provider-specific request fields. Zoo Code validates the JSON, rejects runtime-managed and prototype-sensitive keys, persists it only for OpenAI-compatible profiles, and merges safe fields into streaming, non-streaming, O-family, and single-completion requests.
The settings control uses VS Code-themed components, accessible validation feedback, translations for every supported locale, and unclipped full-height visual baselines for dark, light, high-contrast, and high-contrast-light themes.
Why this change was made
Providers such as Sail Research require request-body metadata to select features such as the
balancedcompletion window. Custom headers cannot express those fields, so users previously needed a proxy. This closes #1104.Impact
Users can configure provider-specific fields such as
{ "metadata": { "completion_window": "balanced" } }directly in an OpenAI-compatible profile without allowing custom JSON to override Zoo Code's model, messages, tools, streaming, reasoning, temperature, or token limits.Related PRs