CaIon c10780e054 fix(relayconvert): keep JSON Schema constraints in tools and structured output sent to Gemini ...

Requests converted for Gemini had their tool parameters and structured
output schemas forced into Gemini's typed Schema, and anything it cannot
hold was dropped silently: const, oneOf, $ref and $defs lost their
meaning, non-string enum values were removed from tool parameters, and
structured output with type arrays or non-string enum values got a 400
from Gemini.

A schema the typed Schema holds is sent exactly as before. Any other
schema now goes unchanged in parametersJsonSchema or responseJsonSchema,
which Vertex AI and the Gemini API v1beta accept. When a model is set to
Gemini API v1, which has no parametersJsonSchema, the schema is cleaned
as before and a conversion warning names what was dropped.
additionalProperties and $schema alone still do not switch fields, so
Claude Code, Codex and MCP tools and OpenAI strict structured output are
sent unchanged. Responses custom tools keep their typed parameters.

Fixes #7455
Refs #7704

2026-10-11 17:16:17 +08:00

..

claude

fix(relaykit): match Claude effort and Gemini 2.5 budgets to each model

2026-10-11 12:42:17 +08:00

gemini

fix(relayconvert): keep JSON Schema constraints in tools and structured output sent to Gemini

2026-10-11 17:16:17 +08:00