Repository navigation
feat(provider): add v4 request settings defaults - #1365
Merged
Merged
Conversation
TheGreatAxios
force-pushed
the
cl-10225-v4-request-settings
branch
from
October 9, 2026 04:37
ae424d1 to
2d60b7f
Compare
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
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.
Summary
stream_options: { include_usage: true }so vendor usage accounting can read usage on stream chunks.chat_template_kwargs.thinkingfor V4 wire efforts (noneoff, any wire effort on), merging into rather than replacing provider-supplied kwargs.Verification
bun run checkpasses on this branch (8446 pass / 1 pre-existing environmental fail, matching the approved combined-tree baseline for the unrelated shell-guard cwd test).src/provider/deepseek-v4-effort.test.ts,src/provider/openai-compatible-adapter.test.tspass (67 pass / 0 fail).Fixes CL-10225