I opened a Cursor conversation and asked some questions about my code. Cursor then answered my queries, allowing me to see which files it was processing as well as its thinking process. However, both the file information and the thinking process are displayed in English rather than Chinese. Before Cursor 2.0 was released, there were no issues with the language of Cursor’s thinking process.
I remember that in earlier versions of Cursor, the thinking process was not displayed at all. Back then, I didn’t realize how important it was to show the thinking process. But now I do—adding the display of the thinking process was definitely an excellent decision by the Cursor team.
—Best wishes from China
Steps to Reproduce
Have a conversation with Cursor and ask it some questions about your code, then review the content of Cursor’s responses.
Hey, thanks for the report. I need a couple of clarifications to better understand the issue.
You said “before Cursor 2.0 there were no issues with the language of the thinking process,” but also “in earlier versions the thinking process wasn’t displayed at all.” Could you clarify:
Did the thinking process appear in Chinese before Cursor 2.0, or was it simply not visible?
Which model are you using (Auto, Claude, GPT‑4, etc.)?
Important: the thinking process language is determined by the AI model, not Cursor’s interface settings. Most models do internal reasoning primarily in English, even if the final reply is in another language. That’s part of their architecture.
If you can, please share a Request ID (chat menu → Copy Request ID) that will help us investigate.
I have always used Cursor in the Agent’s Auto mode. Not long ago, I was using Cursor 1.7, and there were no issues with the language of the thinking process back then. I also mentioned an earlier period, which should date back to around January 2024 or maybe 2023—if I remember correctly, there wasn’t even a display of the thinking process at that time.
Everything worked normally before Cursor 2.0 was released, but it has not been working properly since Cursor 2.0 came out.
