Skip to content

[Docs] Explain OpenAI-compatible custom request fields - #46

Open
zoomote[bot] wants to merge 2 commits into
mainfrom
docs/openai-extra-body-0ckxn8ezfej92
Open

[Docs] Explain OpenAI-compatible custom request fields#46
zoomote[bot] wants to merge 2 commits into
mainfrom
docs/openai-extra-body-0ckxn8ezfej92

Conversation

@zoomote

@zoomote zoomote Bot commented Aug 22, 2026

Copy link
Copy Markdown

​Created by Roomote. Follow up by mentioning @roomote, in the web UI, or in Discord.

What changed

The OpenAI-compatible provider guide now documents the Extra Body setting, includes a Sail Research metadata.completion_window example, explains protected fields and profile-export security, and shows the complete unclipped 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

@edelauna
edelauna marked this pull request as ready for review August 28, 2026 01:14
@zoomote

zoomote Bot commented Aug 28, 2026

Copy link
Copy Markdown
Author

1 documentation mismatch outstanding.

  • Update the protected-field guidance to include response_format and avoid implying every reserved field has a dedicated setting (docs/providers/openai-compatible.md:70).

Reviewed ee6316e


Zoo Code validates the JSON before saving the provider profile and adds the fields to streaming, non-streaming, and single-completion requests. The top-level value must be an object.

Extra Body cannot override fields managed by Zoo Code, including the model, messages, streaming mode, tools, reasoning settings, temperature, and token limits. Use the corresponding Zoo Code setting for those fields. Do not put API keys or other secrets in Extra Body because provider profiles can be exported.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR #1350 now also protects response_format, but this list omits it and the next sentence implies every protected field has a corresponding Zoo Code setting. Please include response format and qualify the guidance (for example, use Zoo Code’s normal controls where available), since no direct setting exists for every reserved field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant