The codebase indexing in the cursor is constantly loading, causing the sidebar agent to be unresponsive and unable to reply to questions

Support Bug Reports
1

Describe the Bug

The codebase indexing in the cursor is constantly loading, causing the sidebar agent to be unresponsive and unable to reply to questions.

Steps to Reproduce

How to disable indexing to allow the agent to function normally.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

版本: 2.0.77 (user setup)
提交: 1.99.3
日期: ba90f2f88e4911312761abab9492c42442117cf0
Electron: 2025-11-13T23:10:43.113Z
ElectronBuildId: 37.7.0
Chromium: undefined
Node.js: 138.0.7204.251
V8: 22.20.0
OS: 13.8.258.32-electron.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

Hey, thanks for the report. Let’s collect some diagnostic information to understand why indexing is getting stuck.

Please share:

  • Network diagnostics: open Cursor Settings > Network > click “Run Diagnostics” and share the results
  • Approximate codebase size: how big is your project? (number of files or directory size)
  • How long it has been indexing: has it been stuck for hours or days?
  • Console errors: press CTRL+Shift+P > “Developer: Toggle Developer Tools” and check the Console tab for any errors

In the meantime, you can try these steps from the troubleshooting guide:

  • Check that your internet connection is stable
  • Restart Cursor
  • If a VPN is enabled, try turning it off

Let me know what you find.

3

Network diagnostics

image
image1016×446 30.9 KB

4

Approximate codebase size：more than 100000

5

The indexing has been stuck for 3 or 4 days.

6

console output

image
image1901×1001 120 KB

7

I use the same Cursor client to connect via remote SSH to different servers. However, on one of the servers, it always stays like this—the agent keeps showing “Planning next moves.”

image
image1119×517 37.6 KB

9

Thanks for the update. It looks like this is a network issue and the ping isn’t going through.

Please try enabling HTTP/2 or HTTP/1.0.

To optimize work with a large codebase, create a .cursorignore file in the root of your workspace:

node_modules/
.git/
dist/
build/

Add any other large or unnecessary directories there as well.
See: Ignore files | Cursor Docs

If the issues persist:

  • Try enabling a VPN
  • Run diagnostics again: Cursor Settings > Network > Run Diagnostics

Let me know if changing the HTTP/2-HTTP/1.0 setting or using a VPN removes the ping error and allows indexing to finish.

10

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.