Below are common issues and their solutions.

Networking Issues

First, check your network connectivity. Go to Cursor Settings > Network and click Run Diagnostics. This will test your connection to Cursor’s servers and help identify any network-related issues that might be affecting AI features, updates, or other online functionality.

Cursor relies on HTTP/2 for AI features because it handles streamed responses efficiently. If your network doesn’t support HTTP/2, you may experience indexing failures and AI feature issues.

This occurs on corporate networks, VPNs, or when using proxies like Zscaler.

To resolve this, enable HTTP/1.1 fallback in app settings (not Cursor settings): press CMD/CTRL + ,, search for HTTP/2, then enable Disable HTTP/2. This forces HTTP/1.1 usage and resolves the issue.

We plan to add automatic detection and fallback.

Resource Issues (CPU, RAM, etc.)

High CPU or RAM usage can slow your machine or trigger resource warnings.

While large codebases require more resources, high usage typically stems from extensions or settings issues.

If you are seeing a low RAM warning on MacOS, please note that there is a bug for some users that can show wildly incorrect values. If you are seeing this, please open the Activity Monitor and look at the “Memory” tab to see the correct memory usage.

If you’re experiencing high CPU or RAM usage, try these steps:

General FAQs