refactor: drop dead max_output_tokens, simplify maxTokens to 32K + pi cap
Qoder's /model/list catalog never returns max_output_tokens (the field does not exist on any entry — only max_input_tokens is present), so the per-model lookup `entry.max_output_tokens || 32768` was dead code that always fell back to the 32768 literal. - models.ts: remove max_output_tokens from QoderModelEntry; maxTokens is now a flat 32768 (matches qodercli's 32e3 fallback). - stream.ts: remove the now-unused maxOutputTokens variable and its always-true branch; maxTokens = 32768, capped lower only by options.maxTokens (e.g. pi compaction passes 40000). pi-ai's maxTokens setting still has an outlet. - stream.ts fallback modelConfig: drop the dead max_output_tokens: 32768 field. qodercli does conditionally send max_tokens (user setting → generation config → 32K fallback), but the field is not required by the upstream API. Keeping it gives pi-ai's options.maxTokens a place to flow through.
This commit is contained in:
+1
-2
@@ -19,7 +19,6 @@ export interface QoderModelEntry {
|
||||
enable?: boolean;
|
||||
display_name?: string;
|
||||
max_input_tokens?: number;
|
||||
max_output_tokens?: number;
|
||||
context_config?: Record<string, { token_count?: number; is_default?: boolean }>;
|
||||
is_vl?: boolean;
|
||||
is_reasoning?: boolean;
|
||||
@@ -589,7 +588,7 @@ export async function updateQoderModelsCache(
|
||||
input: isVL ? ["text", "image"] : ["text"],
|
||||
cost: ZERO_COST,
|
||||
contextWindow: ctxLen,
|
||||
maxTokens: entry.max_output_tokens || 32768,
|
||||
maxTokens: 32768,
|
||||
});
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user