Cursor IDE Too Slow Code Navigation

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Sometimes, it is impossible to navigate through the code in Cursor IDE. Our project is a Golang project and it is a medium sized project, not too small, not too large.

Sometimes, I just click on a type and Cursor does not respond, just loading. In such case, I re-run go mod vendor. If not works, I try “Restarting Language Processor”. Most of the time still not works and I just kill the Cursor process and restart the IDE.

I think I won’t continue with Cursor just because of this navigation problem. I don’t know if anyone else faced a similar issue but it just kills the pace.

Steps to Reproduce

Not sure exactly. Happening from time to time, especially when I give a break and turn back to my computer after a couple of hours.

Expected Behavior

When I click on a type, I expect any IDE to navigate to that type immediately.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.38 (Universal)
VSCode Version: 1.99.3
Commit: fe5d1728063e86edeeda5bebd2c8e14bf4d0f960
Date: 2025-10-06T18:18:58.523Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

Hey, thanks for the report. The Go language server can sometimes hang, especially after breaks when the project state may have changed.

A couple of things that can help beyond what you’ve already tried:

  • Check for large vendor folders or build artifacts that might slow things down; you can exclude them in your .cursorignore file.
  • The “Go: Restart Language Server” command in the Command Palette Cmd+Shift+P is often more effective than restarting the language processor.

You can also switch to newer gopls settings in your workspace settings:

{
    "go.useLanguageServer": true,
    "gopls": {
        "ui.completion.usePlaceholders": true
    }
}

If the issue persists, check the Go extension logs Output panel → Go to understand what’s causing the hangs. It may be related to module resolution or indexing getting stuck on specific files.