Why My Cursor Was Stuck on ‘Generating…’ and How I Fixed It with One Simple Step

As a developer who relies on Cursor for AI-assisted coding, I recently hit a wall where chat responses took forever or never arrived. It was frustrating—my queries just hung on “Generating…” for minutes, despite a solid internet connection and no apparent issues. After diving deep into troubleshooting, I uncovered a workaround that got things back on track fast.

The Core Problem I Encountered

I was using the latest version of Cursor (around 1.0.0 to 1.1.3), and suddenly, the AI chat feature became painfully slow. Responses would stall for several minutes or not come at all, regardless of the model or settings. My connection was fine—speeds over 300 Mbps—and I had “fast requests” enabled, so this wasn’t a usage limit issue. It felt like the app was broken after an update, and I wasn’t alone; others reported similar slowdowns.

My Step-by-Step Troubleshooting Journey

I started by ruling out the basics, based on my experience and community insights. Here’s what I tried in sequence:

• Checked my internet and app version: I confirmed my connection was solid using online speed tests and verified Cursor was up-to-date. This eliminated network or version mismatch as the cause.
• Disabled extensions temporarily: I ran Cursor with extensions disabled using the command cursor --disable-extensions in my terminal. Unfortunately, this didn’t resolve the issue—responses were still slow.
• Inspected console logs: I opened Developer Tools in Cursor with the command Developer: Toggle Developer Tools and checked the console tab for errors. I saw repetitive messages like “Error fetching git upstream URL” and “ResizeObserver loop completed with undelivered notifications,” which hinted at underlying conflicts but didn’t point to a clear fix.

Despite these steps, the problem persisted, making me wonder if a recent update had introduced a bug.

The Simple Fix That Finally Worked

After more digging, I discovered that disabling extensions wasn’t enough—I needed to uninstall certain ones completely. Here’s how I did it:

• Identified and uninstalled problematic extensions: I removed extensions like the ChatGPT connector or others that might interfere with AI responses. In my case, uninstalling them through Cursor’s extensions panel was key.
• Reinstalled selectively: After uninstalling, I restarted Cursor and saw immediate improvements. Responses were fast again! I then reinstalled the extensions one by one to test, and everything kept working smoothly.

This approach resolved the issue for me, and it seems extensions were causing conflicts that disabling didn’t fully address. If you’re facing this, start by uninstalling non-essential extensions, then reintroduce them cautiously.

Key Takeaways for a Smoother Experience

From this ordeal, I learned that extension conflicts can sneakily slow down Cursor’s AI features. Always keep your app updated, but if slowdowns hit after an update, try uninstalling extensions first. Also, while a developer mentioned a potential fix in an upcoming release, this workaround is a reliable band-aid for now. As an AI tool enthusiast, I’m back to coding efficiently—hopefully, this helps you too!