Overview - Ai

ai

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
fix/openai-strict-schema-fallback
06cd9959 Merge dc686f80a845a36bf3491405b8763bfd46f66653 into e441a6f2695bdf99b8b24685b32ce3bd1145cfcd
by Alem Tuzlak
Succeeded
fix/openai-strict-schema-fallback
06cd9959 ci: apply automated fixes
by autofix-ci...
Succeeded
fix/openai-strict-schema-fallback
a15cb586 Merge 42439ad8e6bf39eae9b190072df1f3bc9f4fb779 into e441a6f2695bdf99b8b24685b32ce3bd1145cfcd
by Alem Tuzlak
Succeeded
fix/openai-strict-schema-fallback
a15cb586 fix(openai): emit strict:false for tools whose schema is outside OpenAI's strict subset The Responses and Chat Completions tool converters forced `strict: true` on every function tool. When a tool's schema uses keywords OpenAI's strict Structured Outputs subset doesn't support (oneOf/allOf/not/$ref/$defs — routinely emitted by MCP servers such as Notion), the API rejected the entire request with `400 Invalid schema for function '…'`, breaking every run that included such a tool. Detect schemas outside the strict subset (`isStrictModeCompatible`) and emit those tools with `strict: false` — the schema is passed through (only unsupported `format` keywords stripped) so the tool stays callable. Schemas that fit the strict subset keep `strict: true` and the existing coercion.
by Alem Tuzlak