Codebase Stuck in Indexing State

Bug Reports
1

Codebase Stuck in Indexing State

image
image1734×898 82.9 KB

Description

I’m experiencing an issue where the codebase functionality in Cursor is constantly stuck in the indexing state. The indexing process never completes, making it impossible to use the codebase features effectively.

Steps to Reproduce

  1. Open a project in Cursor
  2. Wait for the codebase indexing to start
  3. The indexing process begins but never completes, staying in the “indexing” state indefinitely

Impact

:prohibited: This issue prevents me from using Cursor’s codebase features, which significantly impacts my workflow.

Environment

  • OS: macOS (based on electron info)
  • Cursor Version: 0.48.6 (Universal)
  • Commit: 1.96.2
  • Date: 1649e229afdef8fd1d18ea173f063563f1e722e0
  • Electron: 2025-03-31T05:01:56.506Z (1 day ago)
  • ElectronBuildId: 34.3.4
  • Chromium: undefined
  • Node.js: 132.0.6834.210
  • V8: 20.18.3
  • OS: 13.2.152.41-electron.0

Additional Information

I’ve tried waiting for extended periods, but the indexing process never completes. This makes it impossible to use any features that rely on the codebase being properly indexed.

2

Hey, unfortunately, we are currently facing some issues with codebase indexing, which may cause the Handshake Failed error, and some degraded performance in the features that rely on it.

We hope to have those solved soon, but you can track the status of this on status.cursor.com

Apologies for any inconvenience this may cause!

3

Thank you for the response. I appreciate the acknowledgment of the issue.

However, I would like to emphasize that this is not an isolated incident. The codebase indexing and related services have been experiencing persistent and frequent outages over the recent period, which is severely impacting my productivity and workflow.

While I understand technical issues can arise, the current level of instability is concerning:

  1. The continuous “Handshake Failed” errors and indefinite indexing states make core features unusable
  2. These disruptions are happening frequently enough that it’s affecting my daily work
  3. Having to constantly check status.cursor.com to determine if I can use the tool is not a sustainable workflow

As a user who relies on Cursor for professional work, I would strongly urge prioritizing system stability and service availability. The current situation where core functionality is regularly unavailable makes it difficult to depend on Cursor as a primary development tool.

Could you please share any plans for improving the overall stability of the service beyond just fixing the current indexing issue? Is there an estimated timeline for when we can expect more reliable service?

Thank you for your attention to this matter.