mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
kimi k2.5 error #960
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @leslie2046 on GitHub (Jan 30, 2026).
Self Checks
Dify version
1.11.4
Plugin version
0.1.0
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
✔️ Error log
2026-01-30 17:41:55.356 ERROR [Thread-111953 (_generate_worker)] [base.py:305] 5db29c4afe435c168479233db823fa38 - Error in stream response for plugin {'code': -500, 'message': '{"message":"{\"args\":{\"description\":\"[models] Error: API request failed with status code 400: {\\\"error\\\":{\\\"message\\\":\\\"thinking is enabled but reasoning_content is missing in assistant tool call message at index 2\\\",\\\"type\\\":\\\"invalid_request_error\\\"}}\"},\"error_type\":\"InvokeError\",\"message\":\"[models] Error: API request failed with status code 400: {\\\"error\\\":{\\\"message\\\":\\\"thinking is enabled but reasoning_content is missing in assistant tool call message at index 2\\\",\\\"type\\\":\\\"invalid_request_error\\\"}}\"}","error_type":"PluginInvokeError","args":null}', 'data': None}
@dosubot[bot] commented on GitHub (Jan 30, 2026):
This error happens because the kimi k2.5 (and similar "thinking mode" models) require a reasoning_content field in assistant messages during tool calls. Older plugin versions—including 0.1.0—don't extract or include this field, which triggers the 400 error you’re seeing. This isn't a configuration issue; it's a gap in the plugin's implementation.
A fix was merged in the dify-official-plugins repo (PR #2298, Dec 2025) that extracts reasoning content from ... blocks and includes it as reasoning_content in the API request. To resolve the error, upgrade your dify-official-plugins to at least version 0.0.37 or later, where this patch is present. The Dify core platform also received a related fix (PR #30083, Jan 2026) to ensure reasoning_content is handled correctly [details](https://github.com/langgenius/dify-official-plugins/pull/2298) [core fix](https://github.com/langgenius/dify/pull/30083).
If you can't upgrade, you would need to patch the plugin code to extract reasoning_content from tags and include it in the assistant tool call message. There are no runtime flags or config changes that can bypass this; it requires a code update.
Let me know if you need help with the patching process or want more details on where to apply the fix.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other