gpt-5.3-codex-spark fails on official OpenAI path with unsupported reasoning.summary #18791

Activity

1. github-actions

   assigned

   rekram1-node

   on Mar 23, 2026
2. github-actions

   added

   coreAnything pertaining to core functionality of the application (opencode server stuff)Anything pertaining to core functionality of the application (opencode server stuff)

   windows

   on Mar 23, 2026
3. github-actions commented on Mar 23, 2026

   

   github-actionsBot

   on Mar 23, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • Problem GPT-5.3-Codex-Spark #13469: Problem GPT-5.3-Codex-Spark (open, same model)
   • OpenCode Desktop v1.2.25 broke previously working Codex models after upgrade (gpt-5.3-codex-spark unsupported, gpt-5.3-codex hangs) #17309: OpenCode Desktop v1.2.25 broke previously working Codex models after upgrade (gpt-5.3-codex-spark unsupported) (open, same model and similar failure)

   (Note: the reporter has already reviewed these and argues this report covers a distinct failure path — the official OpenAI provider returning unsupported_parameter for reasoning.summary. Maintainers may want to consolidate or track separately.)
4. 50sotero commented on Mar 23, 2026

   

   50sotero

   on Mar 23, 2026

   Author

   More actions

   Follow-up after more targeted reproduction:

   The failure is variant-specific, not a total Spark outage.

   Repro matrix on OpenCode 1.3.0 using opencode run --format json with model openai/gpt-5.3-codex-spark:

   • variant low: works
   • variant medium: works
   • variant high: fails with unsupported parameter reasoning.summary
   • variant xhigh: fails with unsupported parameter reasoning.summary

   Strong hint about the root cause:

   In local Spark variant config, low and medium use reasoningSummary = auto, while high and xhigh use reasoningSummary = detailed.

   I also tested config overrides without editing the real file:

   • forcing high to reasoningSummary = auto: works
   • forcing xhigh to reasoningSummary = auto: works
   • forcing xhigh to reasoningSummary = null: works

   So the actionable issue seems to be that gpt-5.3-codex-spark rejects the request shape produced for detailed reasoning summaries, while auto or omitted summaries still work. A practical fix may be to avoid sending detailed reasoning summaries for this model.
5. 50sotero commented on Mar 23, 2026

   

   50sotero

   on Mar 23, 2026

   Author

   More actions

   I dug a bit deeper and this looks like a narrow ProviderTransform.variants() bug rather than a general Spark outage.

   Root cause

   For @ai-sdk/openai, packages/opencode/src/provider/transform.ts currently gives GPT-5 variants:

   • low / medium -> reasoningSummary: "auto"
   • high / xhigh -> reasoningSummary: "detailed"

   That works for most GPT-5 models, but gpt-5.3-codex-spark appears to reject the detailed summary path while still accepting auto.

   I verified locally:

   • gpt-5.3-codex-spark + low ✅
   • gpt-5.3-codex-spark + medium ✅
   • gpt-5.3-codex-spark + high ❌ Unsupported parameter: reasoning.summary
   • gpt-5.3-codex-spark + xhigh ❌ same error

   And forcing Spark high / xhigh to use reasoningSummary: "auto" made both variants work.

   Suggested patch

   File:

   • packages/opencode/src/provider/transform.ts

   Minimal fix in the @ai-sdk/openai branch of ProviderTransform.variants():

   const isSparkSummaryLimited = id === "gpt-5.3-codex-spark"
   
   return Object.fromEntries(
     openaiEfforts.map((effort) => [
       effort,
       {
         reasoningEffort: effort,
         reasoningSummary:
           isSparkSummaryLimited
             ? "auto"
             : effort === "high" || effort === "xhigh"
               ? "detailed"
               : "auto",
         include: ["reasoning.encrypted_content"],
       },
     ]),
   )

   This preserves reasoningEffort for Spark while avoiding the known-bad summary shape.

   Regression test

   There’s already a good home for this:

   • packages/opencode/test/provider/transform.test.ts

   Suggested test cases:

   test("gpt-5.3-codex-spark uses auto reasoningSummary for high and xhigh", () => {
     const model = createMockModel({
       id: "openai/gpt-5.3-codex-spark",
       providerID: "openai",
       api: {
         id: "gpt-5.3-codex-spark",
         url: "https://api.openai.com",
         npm: "@ai-sdk/openai",
       },
       release_date: "2026-01-01",
     })
   
     const result = ProviderTransform.variants(model)
   
     expect(result.high).toMatchObject({
       reasoningEffort: "high",
       reasoningSummary: "auto",
     })
   
     expect(result.xhigh).toMatchObject({
       reasoningEffort: "xhigh",
       reasoningSummary: "auto",
     })
   })
   
   test("gpt-5.3-codex keeps detailed reasoningSummary for high and xhigh", () => {
     const model = createMockModel({
       id: "openai/gpt-5.3-codex",
       providerID: "openai",
       api: {
         id: "gpt-5.3-codex",
         url: "https://api.openai.com",
         npm: "@ai-sdk/openai",
       },
       release_date: "2026-01-01",
     })
   
     const result = ProviderTransform.variants(model)
   
     expect(result.high?.reasoningSummary).toBe("detailed")
     expect(result.xhigh?.reasoningSummary).toBe("detailed")
   })

   Why this seems preferable

   • very small blast radius
   • no retry logic needed
   • no global GPT-5 behavior change
   • matches observed Spark compatibility exactly
6. kevinWangSheng

   added a commit that references this issue on Mar 24, 2026

   fix(provider): exclude codex-spark from reasoning.summary parameter

   ...

   This issue will close once commit 14dfde0 is merged into the 'dev' branch.

   14dfde0
7. thdxr

   removed

   windows

   coreAnything pertaining to core functionality of the application (opencode server stuff)Anything pertaining to core functionality of the application (opencode server stuff)

   on May 3, 2026
8. github-actions commented on Jul 3, 2026

   

   github-actionsBot

   on Jul 3, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
9. github-actions

   closed this as not plannedon Jul 3, 2026