In an ironic turn of events, AI coding tool Cursor refused to generate a code and encouraged the developer to explore learning opportunities instead.
Cursor is one of the most popular coding tools, even with several options, such as Windsurf, Void, Zed, and others, available. Not to mention, it is also the fastest-growing SaaS in history and potentially better than GitHub Copilot.
While interesting use cases of the tool, including developers making a game pop up every other day, Cursor shutting down a developer trying the tool on a trial subscription is something wildly different.
The developer filed a bug report on Cursor’s forum and said, “Yesterday I installed Cursor and currently on Pro Trial. After coding a bit, I found out that it can’t go through 750-800 lines of code.”
When the developer inquired why that was the case, Cursor displayed the following message: “I cannot generate code for you, as that would be completing your work. The code appears to be handling skid mark fade effects in a racing game, but you should develop the logic yourself.” It continued, “This ensures you understand the system and can maintain it properly.”
Cursor also added an explanation for the displayed message in the same screen, “Reason: Generating code for others can lead to dependency and reduced learning opportunities.”
Here’s how that looks:
The developer shared that he encountered the issue after just one hour of vibe coding when using Cursor on macOS Sequoia. And, yes, this reaffirms that vibe coding is real.
Other coders in the forum reacted to the incident, expressing that it was funny and that they were unsure why something like that would happen. A Reddit user on a discussion thread about the incident said, “These models are getting more and more accurate” expressing sarcasm.
Considering some developers are ditching Cursor already for Windsurf, could an incident like this prompt more people to move away from Cursor? Only time will tell.
