fix(v2): pin strict:false on function tools that omit it - #295

Summary

• What changed? The V2 adapter's language-model wrapper now defaults strict:false onto function tools that don't declare strict, before @ai-sdk/openai serializes them into the Responses request body. Explicit strict values are preserved.
• Why is this needed? The SDK only writes strict when a tool declares it, and the Codex backend treats an omitted flag as strict-mode structured output: every declared schema property becomes required. OpenCode's task tool marks sessionID optional, so the model fabricates one and fresh subagent calls die with Subagent session not found. Reported against OpenCode 2.0.24 + plugin 6.28.0; the reporter verified a local strict:false patch restores subagent round-trips.

 doGenerate / doStream options
   providerOptions.openai   store:false, drop previousResponseId/conversation   (existing)
+  tools[]                  function tools get strict:false when unset

Testing

• npm run lint

• npm run build

• npm run typecheck

• npm test

• npm test -- test/doc-parity.test.ts

• Not applicable

• Before: new it.each(doGenerate, doStream) case fails — the captured Responses body serializes task with no strict field:

expect(tools.find((tool) => tool.name === "task")).toMatchObject({ strict: false })
  → received { type: "function", name: "task", description, parameters, /* no strict */ }
Tests  2 failed | 24 skipped

• After: same run passes — the wire body carries strict:false on the unmarked tool and keeps strict:true on an explicitly-strict tool:

Test Files  1 passed (1)   test/opencode-v2.test.ts
Tests  26 passed (26)

Note on npm test: this Windows dev box shows 25 pre-existing failures in storage/paths/installer/stress suites (POSIX mode bits, FIFOs, ADMINI~1 8.3 realpath, fsync/lock semantics). Reproduced identically on clean main — unrelated to this diff. The touched suite is fully green.

Docs and Governance Checklist

• README updated (if user-visible behavior changed)
• docs/getting-started.md updated (if onboarding flow changed)
• docs/tools-and-cli.md updated (if the codex-* tool or CLI surface changed)
• docs/configuration.md / docs/development/CONFIG_FIELDS.md updated (if config keys or env vars changed)
• docs/upgrade.md updated (if migration or rename behavior changed)
• SECURITY.md and CONTRIBUTING.md reviewed for alignment

No docs touched — internal request-shaping fix, no user-visible surface change beyond the bug being gone.

Compliance Confirmation

• This change stays within the repository scope and OpenAI Terms of Service expectations.
• This change uses official authentication flows only and does not add bypass, scraping, or credential-sharing behavior.
• I updated tests and documentation when the change affected users, maintainers, or repository behavior.

Notes

• Linked issue: Closes [BUG] OpenCode V2 subagent calls fabricate sessionIDs when Responses tool strictness is omitted #293
• Follow-up work or rollout notes: two commits — the failing repro test lands first, then the one-function fix, per the repo's TDD cadence.

Merge Danger

Door: two-way — a one-line default inside the existing options transform; revert restores prior behavior.

Blast Radius: V2 function-tool serialization only. V1 path untouched; tools that explicitly set strict keep their value; provider-defined tools are passed through unmodified.

Summary by CodeRabbit

• Bug Fixes
  • Function tools without an explicitly configured strictness setting are now sent with strictness disabled, for both generated and streamed responses.
  • Explicit strictness settings are preserved, and tool definitions remain unchanged.

note: greptile review for oc-chatgpt-multi-auth. cite files like lib/foo.ts:123. confirm regression tests + windows concurrency/token redaction coverage.

Confidence Score: 5/5

Summary

the v2 adapter adds strict:false to function tools that omit it. explicit values stay unchanged, and provider tools pass through.

• V2 requests keep optional function arguments optional.

_{Reviews (2) · Last reviewed commit: "test(v2): cover explicit strict:false an..." · Reviewed by Greptile}