Files
OmniRoute/tests
ivan_yakimkin be6c3ac662 fix: preserve max_output_tokens for Responses API targets in chatCore sanitization
The common input sanitization in chatCore unconditionally normalizes
max_output_tokens to max_tokens (#994). This works for Chat Completions
targets but breaks Responses API passthrough (source and target both
openai-responses), because:

1. chatCore replaces max_output_tokens with max_tokens
2. Same-format requests skip the translator entirely
3. max_tokens reaches the upstream, which rejects it with
   'Unsupported parameter: max_tokens'

The fix makes the normalization conditional: skip it when the target
format is openai-responses, where max_output_tokens is the canonical
field. The existing openaiToOpenAIResponsesRequest translator (#1245)
still handles the openai → openai-responses path correctly.

Adds a test that verifies max_output_tokens is not normalized to
max_tokens when routing to a Responses API target.
2026-04-16 13:26:49 +03:00
..