You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
→ Read opencode.json
Error: File not found: D:\Projects\LLM_Workspace\bear_party\opencode.json
Missing reasoning_content field in the assistant message at message index 2. For more information, please refer to https://api-docs.deepseek.com/guides/thinking_mode#tool-calls
$ dir /b
Get-ChildItem: Cannot find path 'D:\b' because it does not exist.
Missing reasoning_content field in the assistant message at message index 8. For more information, please refer to https://api-docs.deepseek.com/guides/thinking_mode#tool-calls
Above is the issue where the thinking parameter cannot be used and will result in an error in thinking mode. Please help me
Missing reasoning_content field in the assistant message at message index 32.
For more information, please refer to https://api-docs.deepseek.com/guides/thinking_mode#tool-calls
So this does not seem limited to deepseek-chat with thinking.type=enabled; it also appears in custom subagent flows with deepseek-reasoner when tool calls are involved.
Activity
github-actions commentedon Jan 19, 2026
This issue might be a duplicate of existing issues. Please check:
reasoning_content#4947: DeepSeek 3.2: Missingreasoning_contentFeel free to ignore if none of these address your specific case.
tongsh6 commentedon Mar 10, 2026
I can reproduce the same class of bug in a slightly different setup: a custom local subagent using
deepseek/deepseek-reasonerwith tools enabled.Local agent file:
~/.config/opencode/agents/architect.mdObserved error:
So this does not seem limited to
deepseek-chatwiththinking.type=enabled; it also appears in custom subagent flows withdeepseek-reasonerwhen tool calls are involved.Related issue with more detail:
#8934.github-actions commentedon Jul 6, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.