laantungir/routstrd
1
0
Fork 0
mirror of https://github.com/Routstr/routstrd.git synced 2026-10-05 12:28:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

revert: use max_tokens for chat/completions instead of max_completion_tokens

Browse Source 
Revert the default request-limit field back to legacy max_tokens for
chat/completions (keeping max_output_tokens for the Responses API).
This commit is contained in:
redshift
2026-09-07 14:11:52 +02:00
parent 6499bbd870
commit 6218b20bf9
1 changed files with 3 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/daemon/http/index.ts
+3 -8
View File
@@ -1712,20 +1712,15 @@ export function createDaemonRequestHandler(deps: {
// limit. Without this, the SDK prices at the provider's worst-case
// max_completion_cost, which varies widely across providers (2.3× for
// kimi-k3) and balloons during provider failover. Chat/completions use
// max_completion_tokens (the OpenAI-standard field; legacy max_tokens is
// deprecated and rejected by reasoning models); the Responses API uses
// max_output_tokens.
// max_tokens; the OpenAI Responses API uses max_output_tokens.
if (deps.maxTokens > 0) {
const isResponsesPath = url.pathname.includes("/responses");
if (isResponsesPath) {
if (typeof bodyObj.max_output_tokens !== "number") {
bodyObj.max_output_tokens = deps.maxTokens;
}
} else if (
typeof bodyObj.max_completion_tokens !== "number" &&
typeof bodyObj.max_tokens !== "number"
) {
bodyObj.max_completion_tokens = deps.maxTokens;
} else if (typeof bodyObj.max_tokens !== "number") {
bodyObj.max_tokens = deps.maxTokens;
}
}