Skip to content

fix(ai): require reasoning fields for deepseek assistants - #45075

Merged
rekram1-node merged 4 commits into
v2from
deepseek-reasoning
Aug 25, 2026
Merged

rekram1-node merged 4 commits into
v2from
deepseek-reasoning

Conversation

@rekram1-node

Copy link
Copy Markdown
Collaborator

Summary

  • add the public requireReasoning model compatibility option and expose it in generated client types
  • infer required assistant reasoning from DeepSeek model IDs, the DeepSeek provider, or DeepSeek API endpoints while honoring explicit overrides
  • include an empty configured reasoning field on assistant text and tool-call messages when required, preserving custom field names and existing explicit reasoningField behavior
  • cover model/provider/endpoint detection, custom reasoning fields, explicit opt-out, public schema decoding, and model resolution

Test plan

  • bun test test/provider/openai-chat.test.ts test/provider/openai-compatible-chat.test.ts && bun typecheck from packages/ai
  • bun test test/model.test.ts && bun typecheck from packages/schema
  • bun test test/model-resolver.test.ts && bun typecheck from packages/core
  • bun run generate && bun typecheck from packages/client
  • broader bun test test/provider currently encounters unrelated existing Anthropic/OpenRouter recorded-fixture and OpenRouter expectation failures

@rekram1-node
rekram1-node merged commit c2a3b81 into v2 Aug 25, 2026
7 of 8 checks passed
@rekram1-node
rekram1-node deleted the deepseek-reasoning branch August 25, 2026 22:13
jinhuang712 pushed a commit to jinhuang712/opencode that referenced this pull request Sep 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant