Gemini tool schema fails when a tool input is a nullable array

[Role1776]

Bug

When a tool input is declared as a nullable array (type: ["null", "array"]), @ai-sdk/google's convertJSONSchemaToOpenAPISchema splits it into anyOf: [{ type: "array" }] but leaves a sibling items field dangling at the parent level.

Gemini rejects the resulting function declaration because items sits outside the array branch, producing a schema error for any tool whose input is a nullable array.

Impact

Any opencode tool whose input schema contains type: ["null", "array"] fails against Google Gemini (@ai-sdk/google / @ai-sdk/google-vertex).

Suggested fix

Before sending the request, fold the sibling items into the array-typed branches of any union (anyOf/oneOf/allOf) so the generated function declaration carries items inside the array branch. See packages/opencode/src/session/llm/request.ts.

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Google Gemini 400 schema error when function call has nullable union types #34130: Same root cause — @ai-sdk/google's convertJSONSchemaToOpenAPISchema produces malformed anyOf schemas for nullable types, causing Gemini to reject tool/function declarations with a 400 schema error. That issue covers the required field being left outside the object branch; this issue covers items being left outside the array branch. They may be worth fixing together.