Cursor Documentation
  1. Troubleshooting
Cursor Documentation
  • Get Started
    • Introduction
    • Installation
    • FAQ
  • Guides
    • Editor Migration
      • Migrate from VS Code
      • Migrate from JetBrains IDEs
    • Languages & Frameworks
      • JavaScript & TypeScript
      • iOS & macOS (Swift)
      • Java
  • Editor
    • AI Commit Message
    • Notepads (Beta)
    • Keyboard Shortcuts
    • Tab
      • Overview
      • Tab vs GitHub Copilot
      • Auto-import
      • Advanced Features
    • Chat
      • Overview
      • Agent mode
      • Ask mode
      • Custom modes
      • Tools
      • Apply
    • ⌘K
      • Overview
      • Terminal Cmd K
  • Context
    • Codebase Indexing
    • Rules for AI
    • Ignore Files
    • Model Context Protocol
    • @ Symbols
      • Overview
      • @Files
      • @Folders
      • @Code
      • @Docs
      • @Git
      • @Web
      • @Definitions
      • @Link
      • @Lint Errors
      • @Lint Errors
      • @Recent Changes
      • @Cursor Rules
      • @Notepads
      • @Summarized Composers
      • #Files
      • /command
  • Account
    • Plans & Usage
    • Dashboard
    • Billing
    • Business
      • Get Started
      • Members + Roles
      • Analytics
      • SSO
  • Settings
    • Models
    • Custom API Keys
    • Early Access Program
  • Troubleshooting
    • Common Issues
    • Troubleshooting Guide
    • Getting a Request ID
  1. Troubleshooting

Troubleshooting Guide

Technical guide for gathering logs, errors and system info when reporting Cursor issues
Sometimes, Cursor may unexpectantly have some issues. This can be due to a number of reasons, including extensions, app data, or your system. While we work hard to ensure Cursor is as stable out of the box as possible, if these issues happen, you can try the following steps to resolve them.
Extension Data
Application Data
Uninstalling
Reporting an Issue
Steps to report an issue to the Cursor team

Troubleshooting#

1. Extension Data#

If you are experiencing issues with individual extensions, you can try uninstalling and reinstalling them to reset any data they may have stored. Also check your settings to see if you have any configuration for the extensions that would remain after uninstalling and reinstalling them.

2. Clearing App Data#

WARNING:
This will delete your app data, including your extensions, themes, snippets and any other data related to your installation. Consider exporting your profile to ensure this data is not lost.
To allow your installation to be restored between updates, and between reinstallation, Cursor keeps your app data outside of the app itself. This means that if you uninstall Cursor, you can reinstall it and it will restore your app data from the previous installation.
If you would like to clear your app data, you can do so by following these steps:
Windows: Run the following commands in Command Prompt:
rd /s /q %USERPROFILE%\AppData\Local\Programs\cursor*
rd /s /q %USERPROFILE%\AppData\Local\Cursor*
rd /s /q %USERPROFILE%\AppData\Roaming\Cursor*
rd /s /q %USERPROFILE%\cursor*
MacOS: Run sudo rm -rf ~/Library/Application\ Support/Cursor and rm -f ~/.cursor.json in Terminal.
Linux: Run rm -rf ~/.cursor ~/.config/Cursor/ in Terminal.

3. Uninstalling Cursor#

While we never want you to have to reinstall Cursor, if you are experiencing issues, this can sometimes help.
To uninstall the Cursor app, you can do the following:

Windows#

Search for Add or Remove Programs Start Menu, find “Cursor” list, and click “Uninstall”.

MacOS#

Open the Applications folder, find “Cursor” in the list, and right click and select “Move to Trash”.

Linux#

Open the Applications folder, find “Cursor” in the list, and right click and select “Move to Trash”.

4. Reinstalling Cursor#

If you have uninstalled Cursor, you can reinstall it by going to the Downloads page and downloading the latest version. If you have not cleared your app data, this should restore your app to the state it was in when you uninstalled it. Otherwise, you will have an entirely fresh install of Cursor.

Reporting an Issue#

If the above steps don’t help, please let us know in the forum and we’ll be happy to help diagnose the issue.
Cursor Forum
Report an bug or issue on the Cursor forum
For the best chance at a quick resolution, please provide as much of the following information as you can, to help the team resolve the issue for you and othersß∂:

Screenshot of Issue#

Capture a screenshot of the issue, making sure to redact any sensitive information.

Steps to Reproduce#

Document the exact steps needed to reproduce the issue.

System Information#

Retrieve system information from:
Cursor > Help > About

Request IDs#

Click to view our guide on gathering request IDs

Console Errors#

Check developer tools console errors, by running this in the command palette:
Developer: Toggle Developer Tools

Logs#

Access Cursor’s logs by running this in the command palette:
Developer: Open Logs Folder
Modified at 2025-03-31 03:27:25
Previous
Common Issues
Next
Getting a Request ID
Built with