# Kimi 2.6 custom model - Provider returned error: {"error":{"message":"thinking is enabled but reasoning\_content is missing **URL:** \ **Category:** Bug Reports\ **Tags:** byok\ **Created:** [May 2, 2026, 5:30pm UTC](https://forum.cursor.com/t/kimi-2-6-custom-model-provider-returned-error-error-message-thinking-is-enabled-but-reasoning-content-is-missing/159625 "2026-05-02T17:30:17Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [May 2, 2026, 5:49pm UTC](https://forum.cursor.com/t/kimi-2-6-custom-model-provider-returned-error-error-message-thinking-is-enabled-but-reasoning-content-is-missing/159625/5 "2026-05-02T17:49:29Z")
Hey, this is a known limitation of the BYOK path for thinking models like Kimi and DeepSeek. After the first tool call, `reasoning_content` gets dropped from the history, and the provider Moonshot rejects the next request. The same symptom is discussed here: [Kimi/kimi-k2.5 cannot be called to execute tool calls in cursor](https://forum.cursor.com/t/kimi-kimi-k2-5-cannot-be-called-to-execute-tool-calls-in-cursor/155922) and here for DeepSeek with the same root cause: [Compatibility with DeepSeek model's design to return reasoning content after tool calls?](https://forum.cursor.com/t/compatibility-with-deepseek-models-design-to-return-reasoning-content-after-tool-calls/158905). We’re tracking the issue, but I can’t share an ETA for a fix yet. I’m going to close this thread as a duplicate. For updates, please follow the DeepSeek thread since it’s more active. Workaround for now: if you can, turn off thinking mode in Moonshot for this model, or use a non-reasoning model. Tool calls should work fine then. --- _[View the full topic](https://forum.cursor.com/t/kimi-2-6-custom-model-provider-returned-error-error-message-thinking-is-enabled-but-reasoning-content-is-missing/159625)._