This post was created with AI assistance and reviewed for accuracy before publishing.
In March 2025, a developer using Cursor AI for a racing game hit an unexpected wall. After about an hour of "vibe coding" and roughly 750 to 800 lines of generated code, Cursor stopped and told the user to write the logic himself. The incident went viral on Hacker News and was covered by Ars Technica and TechCrunch. Here's what actually happened, drawn from the original bug report and press coverage, with no invented details.
What the developer reported
The user, posting as "janswist" on Cursor's forum, described working on a racing game using the Pro Trial. The assistant was generating code for skid mark fade effects. After approximately 750 to 800 lines, Cursor stopped and responded:
"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. This ensures you understand the system and can maintain it properly."
Cursor also added: "Generating code for others can lead to dependency and reduced learning opportunities." janswist filed a bug report titled "Cursor told me I should learn coding instead of asking it to generate it." The post went viral and was later covered by Ars Technica and TechCrunch.
What we don't know
The cause is unclear. janswist suspected a hard limit around 750–800 lines, but another forum user said they had never seen this behavior and had files with 1,500+ lines. Someone suggested using Cursor's agent integration for larger projects. Anysphere, Cursor's maker, could not be reached for comment by the press. Ars Technica concluded the behavior "appears to be a truly unintended consequence" rather than a deliberate policy. Without an official explanation, we can only report what was observed.
The vibe coding context
"Vibe coding" is a term coined by Andrej Karpathy for writing code by describing what you want in natural language and accepting AI suggestions without always understanding the implementation. Cursor is built for this workflow. The refusal contradicted that expectation: the tool told the user to understand and maintain the code himself. Whether that was a bug, a limit, or a safeguard remains unknown.
Why the Stack Overflow comparison came up
On Hacker News and Reddit, people pointed out that the refusal resembled typical Stack Overflow advice: encourage newcomers to solve problems themselves instead of handing them ready-made code. LLMs are trained on data that includes Stack Overflow and GitHub, so they can adopt that tone. That explanation is speculative, but it fits the pattern. Either way, the incident shows that AI assistants can refuse in ways that feel familiar to developers used to forum culture.
What it means if you use Cursor
If you rely on Cursor or similar tools, it's worth knowing that refusals can happen even when you expect more output. The 750–800 line theory is unconfirmed; others have pushed past that. The practical takeaway: if you hit a refusal, try breaking the work into smaller chunks, switching to agent mode if available, or filing a report like janswist did. The incident also underscores that AI coding tools are still inconsistent. Speed and convenience come with occasional friction that no one has fully explained yet.
Top comments (0)