⚠️ shared externally

At Cursor, we strive to provide users with the best possible experience, including making the app highly efficient. At the same time, a wide variety of setups exist, and while we can address issues we are aware of, some require users to report them with additional context to help us investigate. Below is a list of tools you can use to gather additional information, which will significantly help us fix the performance bug and improve the experience for all users.

If nothing below works, please share as many details as possible about the steps that usually lead to performance problems, and provide details about your setup, including which extensions are installed, the model you typically use, the language you work with most, etc. Sometimes, this information is enough for us to reproduce the problem.

The tools below aim to cover the UI process unresponsiveness. Quite often, the primary contributor to suboptimal performance is rogue extensions. As a quick check, it is possible to reload with all extensions disabled to verify it.

MacOS: check the flavor

If you are on M1-M4 (a.k.a. Apple Silicon Mac), your “About version” should show arm64; if it does not, please go to the https://cursor.com/downloads webpage and download the arm64 flavor. It can make a massive difference in performance, especially if you experience very slow UI after every update.

Chrome Performance Trace

Grab a Chrome Performance Trace from your window.

1. Open the devtools if they are not already open. You can find them under the Cursor Help menu.

1. (Optional) Pop the devtools out into another window by clicking the 3 vertical dots and then the leftmost icon.

1. Navigate to the Performance tab. If your window is narrow this may require clicking on the double arrows.

1. Click the record button in the upper left. This will begin recording a performance trace.

1. Do whatever you were doing before that caused lag / stutter / freeze. Try to capture multiple instances of the bad behavior.

2. When the buffer is getting full or you’ve grabbed a few instances, hit the Stop button.

1. (Optional) Take a look at the profile. If you have a hunch about the problem, take a look at the Annotations tab on the left side. Navigate around and Annotate the profile descriptions of what you were doing or what your suspicions are.

1. Hit the Save Profile button and select Save trace. The default name is fine, as it includes a timestamp, but feel free to add even more context to the filename.

1. Share the collected profile with us.

CPU profiler

If the method above does not work - you can use builtin CPU profiler.

1. Press Cmd + Shift + P and type “Developer: Start CPU Profiler”