Codebase indexing stucks for a dedicated remote SSH connection

Hi, thanks for reporting an issue with Cursor.

Before you report this, we’d appreciate if you can search this forum to see if this issue has already been reported.

If you have done so, please check this box.
on

Describe the Bug

After opening the remote connection to a dedicated SSH host, indexing stucks completely with “Indexing…”. No progress bar or error is shown. The problem arises after adding several MB of markdown based documentation to the project. Even after removing the documentation folder from the workspace and completely removing the .cursor-server directory at the remote host, the problem persists. It seams to be related to the cloud component of the indexing feature. Indexing on other remote hosts or local projects seems to work without any problem.

Steps to Reproduce

Add several MB markdown documentation to a project on a remote SSH host.

Expected Behavior

Indexing should complete after some time or show an error if any limit is reached.

Operating System

MacOS
Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 0.44.9
VSCode Version: 1.93.1
Commit: 316e524257c2ea23b755332b0a72c50cf23e1b00
Date: 2024-12-26T21:58:59.149Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 24.2.0

Additional Information

Without codebase indexing cursor is useless for any project on this specific remote host.

Does this stop you from using Cursor

Yes - Cursor is unusable

Solved: Codebase Indexing No Longer Working Inside Dev Containers - #23 by i.guinea