Common Issues

While we strive to make Cursor as stable as possible, sometimes issues can arise. Below are some common issues and how to resolve them.

​

Networking Issues (HTTP/2)

Cursor relies on the HTTP/2 protocol for many of it’s AI features, due to it’s ability to handle streamed responses. If HTTP/2 is not supported by your network, this can cause issues such as failure to index your code, and the inability to use Cursor’s AI features.

This can be the case when on corpoorate networks, using VPNs, or using a proxy like Zscaler.

To resolve this, Cursor now comes with a HTTP/1.1 fallback, which is slower, but will allow you to use Cursor’s AI features. You can enable this yourself in the app settings (not the Cursor settings), by pressing CMD/CTRL + , and then searching for HTTP/2.

You should then enable the Disable HTTP/2 option, which will force Cursor to use HTTP/1.1, and should resolve the issue.

We hope to add automatic detection and fallback in the future!

​

Resource Issues (CPU, RAM, etc.)

Some users see high CPU or RAM usage in Cursor, which can cause their machine to slow down, or to show warnings about high RAM usage.

While Cursor can use a lot of resources when working on large codebases, this is usually not the case for most users, and is more likely to be an issue with Cursor’s extensions or settings.

If you’re experiencing high CPU or RAM usage in Cursor, here are steps to diagnose and resolve the issue:

​

General FAQs