Before submitting your bug report

• I've tried using the "Ask AI" feature on the Continue docs site to see if the docs have an answer
• I'm not able to find a related conversation on GitHub discussions that reports the same bug
• I'm not able to find an open issue that reports the same bug
• I've seen the troubleshooting guide on the Continue Docs

Relevant environment info

- OS: win11
- Continue version:1.3.24
- IDE version:VSCodium 1.106.37943
- Model: deepseek v3.2
- config:
  

  
  OR link to agent in Continue hub:

Description

In Agent node Error:Missing reasoning_content field in the assistant message it shows that is caused by a breaking change in Deepseek V3.2: the API now requires a reasoning_content field in each assistant message when using tool/function calling. Dify 1.9.0 does not include this field in the payload, so Deepseek returns a 400 error. This is a known compatibility issue—there are no merged fixes or official workarounds yet, and the community has been actively requesting support for this field and separation of reasoning content from main content, especially for streaming and TTS scenarios (langgenius/dify#14270 (comment), langgenius/dify#12891).

To reproduce

No response

Log output