CURSOR API MiniMax 2.
report a bug
Hello community!
I want to report an issue I encountered when using the MiniMax model through the API in Cursor IDE.
Title: <think> and </think> tags are visibly displayed in chat responses when using the API in Cursor IDE
Problem Description: When integrating the MiniMax model via API Key in Cursor IDE, the internal reasoning tags <think> and </think> appear visible in chat responses. These tags should be hidden from the end user, displaying only the final response content.
Expected behavior:
The <think> and </think> tags should be hidden in the user interface
Only the processed response content should be displayed without internal metadata
Current behavior: Tags appear literally in the text: <think>reasoning text</think>
The model's internal reasoning content is exposed to the user
Technical details:
Model: MiniMax (via API)
Environment: Cursor IDE
Integration method: API Key
Date: February 13, 2026
Impact: Degraded user experience
Content difficult to read due to visible markup
Confusion about response formatting
Evidence: See attached screenshot showing the issue.
I want to report an issue I encountered when using the MiniMax model through the API in Cursor IDE.
Title: <think> and </think> tags are visibly displayed in chat responses when using the API in Cursor IDE
Problem Description: When integrating the MiniMax model via API Key in Cursor IDE, the internal reasoning tags <think> and </think> appear visible in chat responses. These tags should be hidden from the end user, displaying only the final response content.
Expected behavior:
The <think> and </think> tags should be hidden in the user interface
Only the processed response content should be displayed without internal metadata
Current behavior: Tags appear literally in the text: <think>reasoning text</think>
The model's internal reasoning content is exposed to the user
Technical details:
Model: MiniMax (via API)
Environment: Cursor IDE
Integration method: API Key
Date: February 13, 2026
Impact: Degraded user experience
Content difficult to read due to visible markup
Confusion about response formatting
Evidence: See attached screenshot showing the issue.
