fix(provider): guard textVerbosity injection for @ai-sdk/openai-compatible providers - #43915
Merged
neriousy merged 1 commit intoAug 21, 2026
Conversation
…tible providers Only enable the gpt-5.x textVerbosity default for integrations known to implement OpenAI's verbosity parameter (@ai-sdk/openai and @ai-sdk/amazon-bedrock/mantle). Previously the guard excluded only Azure, so generic @ai-sdk/openai-compatible providers (e.g. LiteLLM proxies) received textVerbosity as well. When such a proxy routes to AWS Bedrock behind the scenes, Bedrock rejects the resulting verbosity parameter with litellm.UnsupportedParamsError, breaking every request (including configured fallbacks) to any gpt-5.x model on that provider. This mirrors the existing reasoningSummary guard pattern fixed in anomalyco#21237 / anomalyco#22352, which textVerbosity never received. Fixes anomalyco#43911
neriousy
enabled auto-merge (squash)
August 21, 2026 22:07
Contributor
|
Thanks for the PR! |
Anonymouse8882
pushed a commit
to Anonymouse8882/opencode
that referenced
this pull request
Aug 27, 2026
…tible providers (anomalyco#43915) Co-authored-by: Joel Stucki <joel.stucki@example.com> (cherry picked from commit 3a4c253)
Archipel
pushed a commit
to Archipel/opencode
that referenced
this pull request
Aug 29, 2026
…tible providers (anomalyco#43915) Co-authored-by: Joel Stucki <joel.stucki@example.com>
1056674754
added a commit
to 1056674754/opencode
that referenced
this pull request
Aug 31, 2026
Upstream v1.18.21 (826d9ad, merged at ab828ce) -> v1.18.22 (47b6b6f), 40 commits / 197 files. Upstream superseded the v1.18.21 release commit with ad0bb6d6 (sync release versions for v1.18.21) in the v1.18.22 lineage; merge base is 57fa34f (fix anomalyco#43892), effective input identical to the audited 40-commit range. Functional changes: - fix(opencode): normalize upgrade endpoint (anomalyco#44686) — target is now a required semver field, raw-body upgrade handler dropped; groups/handlers global httpapi + generated SDK (sdk.gen description, types.gen required target, openapi required:["target"]) adopted whole; fork had no global httpapi deltas. - fix: resolve console device URLs (anomalyco#44029) — origin-rooted verification_uri_complete resolved via URL() with HTTP(S) protocol validation in account.ts and core plugin/provider/opencode.ts, with upstream tests for both. - fix(provider): guard textVerbosity injection for @ai-sdk/openai-compatible providers (anomalyco#43915) — adopted onto fork transform.ts; hunks disjoint from GLM/ZhiPu normalization, auto-merged. - fix: bump Amazon Bedrock provider (anomalyco#43909) — 4.0.112 -> 4.0.158. - test(opencode): align unknown finish coverage (anomalyco#43895). - console zen streaming/memory + unblock workspace, stats model normalization + tooltip truncation, app model provider headers, go pricing changes, docs + i18n updates. Conflicts resolved: 30 package.json version bumps (rebranded 1.18.22-sscity), bun.lock (took upstream, rebranded workspace entries via bun install). run-process.test.ts reconciled by hand: the shared "unknown stream finish preserves partial output and continues" test keeps the fork streamError + auto-ok form; upstream's json variant adopted under its upstream name with the middle-step expectation adapted to the fork's stronger semantics — output-less errored streams are retried transparently (adjacent step-starts, no step-finish part), while the with-output unknown-finish path (step-finish reason "unknown" then loop continues) stays covered by the fork json test. Fork retry caps (content-policy maxAttempts) and GLM/ZhiPu transform normalization preserved; fork small_model_fallback generated SDK/OpenAPI surfaces kept, merge-consistent with upstream's upgrade regen. Tests from both sides kept: transform 437, retry 68, account 15, httpapi-global 4, run-process 15, prompt 62, empty-stream 6, core provider-opencode 12, stats inference 11, llm package 328 all pass; typecheck 30/30.
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.
Issue for this PR
Closes #43911
Type of change
What does this PR do?
options()intransform.tssetstextVerbosity: "low"for anygpt-5.xmodel as long asproviderID !== "azure". That guard allows the default through for generic@ai-sdk/openai-compatibleproviders too (e.g. a LiteLLM proxy), which is wrong:verbosityis an OpenAI-specific parameter, and non-OpenAI backends behind such a proxy reject it outright.Concretely, a
gpt-5.6model routed through a LiteLLM@ai-sdk/openai-compatibleprovider to AWS Bedrock ("Bedrock Mantle") fails every request with:This is the same bug class already fixed for
reasoningSummaryin #21237 / #22352 (unconditional injection for gpt-5.x, guarded only against Azure instead of an explicit allowlist).textVerbositynever got the equivalent fix.The fix switches the check from a denylist (
providerID !== "azure") to an allowlist of providers known to actually implementverbosity:@ai-sdk/openaiand@ai-sdk/amazon-bedrock/mantle. Everything else (including@ai-sdk/openai-compatible,@ai-sdk/azure,@ai-sdk/github-copilot) no longer receivestextVerbosity, matching howreasoningSummary/includeare already scoped a few lines above in the same function.How did you verify your code works?
bun test test/provider/transform.test.ts— 411 pass, 0 fail (added an explicitexpect(result.textVerbosity).toBeUndefined()assertion to the existingopenai-compatible gpt-5 models omit Responses-only reasoningSummarytest).bun turbo typecheck— 30/30 packages pass.textVerbosityis correctly omitted from the request and the call succeeds.Screenshots / recordings
N/A — no UI change.
Checklist