fix(openai-adapters): allow disabling stream_options for strict OpenAI-compatible endpoints

[devYRPauli]

Problem

The OpenAI adapter always adds stream_options: { include_usage: true } to streaming requests. Strict OpenAI-compatible endpoints (for example Databricks serving endpoints) reject unknown fields and return 400 unknown field "stream_options", so Continue cannot talk to them even though the endpoint works when called directly.

Fix

Adds an optional streamOptions boolean to the model config, mirroring the existing useResponsesApi opt-out. Default behavior is unchanged: stream_options is still injected when streaming. Setting streamOptions: false skips it, letting strict endpoints work:

models:
  - name: Databricks
    provider: openai
    model: <endpoint>
    apiBase: https://<workspace>/serving-endpoints
    apiKey: <token>
    streamOptions: false

The field is declared in both the openai-adapters schema and the config-yaml model schema, and gated in modifyChatBody (body.stream && this.config.streamOptions !== false).

Test

Added a test asserting stream_options.include_usage is present by default and absent when streamOptions: false. openai-adapter.vitest.ts passes (5 tests).

Fixes #12936.

[chatgpt-codex-connector]

💡 Codex Review

continue/extensions/cli/src/config.ts

Lines 50 to 54 in 4f24ec0

	model: model.model,
	apiKey: model.apiKey,
	apiBase: model.apiBase,
	requestOptions: model.requestOptions,
	env: model.env,

Forward streamOptions from model configs

When a CLI model specifies streamOptions: false (now accepted by the YAML schema), this adapter config drops that field before calling constructLlmApi; OpenAIApi.modifyChatBody therefore sees the default undefined and still adds stream_options, so the new escape hatch does not work for CLI/headless users hitting strict OpenAI-compatible endpoints.

---

continue/docs-site/app/[[...slug]]/page.tsx

Lines 69 to 71 in 4f24ec0

	const target = redirectTo.startsWith("http")
	? redirectTo
	: `/docs${redirectTo}`;

Use standalone docs paths for internal redirects

For internal redirects from docs.json such as /customization -> /customize/overview, this sends users to /docs/customize/overview. The rest of the standalone docs app deliberately strips the /docs prefix via resolveHref, and generated pages live at /customize/overview, so these redirected URLs land on a non-existent route on the docs site.

---

continue/core/core.ts

Line 1136 in 4f24ec0

on("models/fetch", async (msg) => {

Keep the license-key handler while commands still call it

This replaces the only core handler for mdm/setLicenseKey, but the VS Code continue.enterEnterpriseLicenseKey command and IntelliJ AddLicenseKey action still request that message. In those environments, invoking the enterprise license command now reaches no core handler and can no longer validate or save the key.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".