We believe the issue has been addressed. Could you please let us know if you’re facing the issue when using Auto? If so, please make sure to include a Request ID.
We’ve had no further reports of garbled text in auto mode, and after looking up your request ID, I’m not seeing any indication of garbled text either. Would you be able to share a screenshot of what you’re seeing?
I am currently experiencing an issue with the Cursor AI Chat feature. When I enter a prompt, the system starts “thinking” and displays multiple languages or tokens, but it never produces a final response. It seems to get stuck in the thinking phase without completing the task.
Here are some details about my setup:
Operating System: Windows
Cursor Version: (latest version installed)
Internet Connection: Stable
API Key: Properly configured and active
Steps I have already tried:
Restarting Cursor
Creating a new chat
Reinstalling the application
Verifying API configuration
Despite these steps, the issue persists.
Could you please help me identify the cause of this problem? Also, let me know if there are any logs or additional information I can provide to assist in troubleshooting.
Thank you for your support.
Steps to Reproduce
How can you reproduce this bug?
The issue can be reproduced with the following steps:
Open Cursor AI on my windows system
Go to the Chat section
Enter any prompt (even a simple question)
Press Enter to submit
Observed behavior:
The system starts “thinking”
It displays multiple random languages/tokens while generating
However, it never returns a final response
The process seems stuck indefinitely
Expected behavior:
The AI should generate and return a complete response after processing the prompt
This issue happens consistently with every prompt, even very short ones.
Operating System
Windows 10/11
Version Information
IDE Version:
I am using the Cursor IDE (desktop application) on Linux.
Version: (please insert your exact version number here, e.g., 0.xx.x)
Going to close this thread since the original issue reported on March 17th has been resolved. If you face this, please raise a new post and make sure to include a Request ID!