Indexing Codebase Stuck at 0%

Describe the Bug

I have been stuck on Codebase Indexing 0% for over an hour. This is a new project I just dragged into Cursor.

Steps to Reproduce

Dragging in a new project (coded earlier with cursor) into a new project and starting indexing

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.0.0 (Universal)
VSCode Version: 1.96.2
Commit: 53b99ce608cba35127ae3a050c1738a959750860
Date: 2025-06-04T19:21:39.410Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.3.0

Does this stop you from using Cursor

Yes - Cursor is unusable

10 Likes

I just started having this issue too, and thought I was going crazy or having a bug specific to doing a remote SSH workspace (which always seems to behave a bit quirkier with Cursor).

2 Likes

Just want to comment, I’m seeing this as well.

Operating System

Windows 10 x64

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.1.3 (user setup)
VSCode Version: 1.96.2
Commit: 979ba33804ac150108481c14e0b5cb970bda3260
Date: 2025-06-15T06:55:04.603Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19045

I’ve changed the HTTP Compatibility Mode from 2.0 to 1.1 and 1.0
via the Cursor Indexing and Retries output it seems it is simply timing out without providing a clear reason as to why. I have also restarted my PC, it was working fine prior to an hour ago.

2 Likes

Same here

2 Likes

Same here — I am experiencing this issue in an existing project for ~3 hours. Everything had worked about 6 hours ago.

  • Tried different Cursor versions
  • Tried HTTP/1.1 and HTTP/2
  • Tried deleting the existing index (stuck at 99.3%) and rebuilding

Still not indexing: Progress bar stays at 0% and says “Syncing…”

Version: 1.1.3
VSCode Version: 1.96.2
Commit: 979ba33804ac150108481c14e0b5cb970bda3260
Date: 2025-06-15T06:37:42.715Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Linux x64 6.8.0-60-generic

2 Likes

same issue:

Version: 1.1.3
VSCode Version: 1.96.2
Commit: 979ba33804ac150108481c14e0b5cb970bda3260
Date: 2025-06-15T06:55:04.603Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windsows_NT x64 10.0.26100

Bug submitted via app.

Same here, I tried everything to fix it, but nothing worked

Operating System
Windows 10/11

Version: 1.1.3 (user setup)
VSCode Version: 1.96.2
Commit: 979ba33804ac150108481c14e0b5cb970bda3260
Date: 2025-06-15T06:55:04.603Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19045

Output:
2025-06-17 19:43:41.521 [info] Starting fast remote sync.

2025-06-17 19:43:41.539 [info] Total num embeddable files: 120

2025-06-17 19:43:41.541 [info] Root hash: 0b715fcd25635806d860ab5f35d7aa3d2a51c793796117a3fa841d88811d64f3

2025-06-17 19:43:41.541 [info] Starting repository upload from scratch.

2025-06-17 19:43:41.545 [info] Uploading 120 files.

2025-06-17 19:43:41.594 [info] Total number of files to embed: 120

2025-06-17 19:43:41.594 [info] Not aborted

2025-06-17 19:43:41.594 [info] Starting while loop.

2025-06-17 19:43:41.603 [error] Git command failed: git rev-parse --show-toplevel Command failed: git rev-parse --show-toplevel

fatal: not a git repository (or any of the parent directories): .git

2025-06-17 19:43:41.605 [info] syncing batch of 2 files and 366 bytes

2025-06-17 19:43:41.810 [error] Git command failed: git rev-parse --show-toplevel Command failed: git rev-parse --show-toplevel

fatal: not a git repository (or any of the parent directories): .git

2025-06-17 19:43:45.884 [warning] Failed to get branches from remote: Failed to execute git

2025-06-17 19:43:55.124 [error] Error getting git status: Failed to execute git

2025-06-17 19:43:55.128 [error] Error getting git status: Failed to execute git

2025-06-17 19:44:27.514 [error] Git command failed: git rev-parse --show-toplevel Command failed: git rev-parse --show-toplevel

fatal: not a git repository (or any of the parent directories): .git

2025-06-17 19:44:27.603 [error] Git command failed: git rev-parse --show-toplevel Command failed: git rev-parse --show-toplevel

fatal: not a git repository (or any of the parent directories): .git

2025-06-17 19:46:42.352 [warning] Completed job unsuccessfully, will retry: amplify.yaml error: Weird error: ConnectError: [deadline_exceeded] the operation timed out

2025-06-17 19:46:42.352 [warning] Completed job unsuccessfully, will retry: .cursorignore error: Weird error: ConnectError: [deadline_exceeded] the operation timed out

2025-06-17 19:48:34.322 [error] Git command failed: git rev-parse --show-toplevel Command failed: git rev-parse --show-toplevel

fatal: not a git repository (or any of the parent directories): .git

2025-06-17 19:48:39.652 [info] multiCodebaseIndexingJob dispose

2025-06-17 19:48:39.653 [info] Aborting indexing job.

2025-06-17 19:48:39.653 [info] Doing a startup handshake.

2025-06-17 19:48:39.653 [warning] Completed job unsuccessfully, will retry:

1 Like

experiencing the same issues here as well

Version: 1.1.3 (user setup)
VSCode Version: 1.96.2
Commit: 979ba33804ac150108481c14e0b5cb970bda3260
Date: 2025-06-15T06:55:04.603Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

2 Likes

Same here, updated from 0.5 to 1.1 and stuck

Version: 1.1.3
VSCode Version: 1.96.2
Commit: 979ba33804ac150108481c14e0b5cb970bda3260
Date: 2025-06-15T06:37:42.715Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Linux x64 5.4.0-216-generic

Hi, dev here. We’re working on rolling back a bad server update that might be causing this. Stay tuned, I’ll let you know when to try again. Sorry for the bad experience.

8 Likes

Same problem, this is a major issue for me. Working without repo context makes cursor unusable on repos over a handful of small files.

See logs below.

Windows 10 - Cursor 1.1.3

2025-06-17 18:15:43.600 [error] Git command failed: git rev-parse --show-toplevel Command failed: git rev-parse --show-toplevel
fatal: not a git repository (or any of the parent directories): .git

2025-06-17 18:15:45.549 [warning] Completed job unsuccessfully, will retry: .\memory-bank\projectbrief.md error: Bad unexpected error
2025-06-17 18:15:53.046 [error] Git command failed: git rev-parse --show-toplevel Command failed: git rev-parse --show-toplevel
fatal: not a git repository (or any of the parent directories): .git

2025-06-17 18:16:16.776 [warning] Completed job unsuccessfully, will retry: .\memory-bank\productContext.md error: Bad unexpected error
2025-06-17 18:16:16.776 [warning] Completed job unsuccessfully, will retry: .\memory-bank\projectbrief.md error: Bad unexpected error
2025-06-17 18:16:32.037 [warning] Completed job unsuccessfully, will retry: .\memory-bank\projectbrief.md error: Bad unexpected error
2025-06-17 18:16:32.038 [warning] Completed job unsuccessfully, will retry: .\memory-bank\productContext.md error: Bad unexpected error
2025-06-17 18:16:43.374 [error] Git command failed: git rev-parse --show-toplevel Command failed: git rev-parse --show-toplevel
fatal: not a git repository (or any of the parent directories): .git

2025-06-17 18:17:02.211 [error] Error getting git status: Failed to execute git
2025-06-17 18:17:03.290 [error] Error getting git status: Failed to execute git
2025-06-17 18:19:32.686 [warning] Completed job unsuccessfully, will retry: .\memory-bank\projectbrief.md error: Weird error: ConnectError: [deadline_exceeded] the operation timed out
2025-06-17 18:19:32.686 [warning] Completed job unsuccessfully, will retry: .\memory-bank\productContext.md error: Weird error: ConnectError: [deadline_exceeded] the operation timed out
2025-06-17 18:19:39.868 [error] Error getting git status: Failed to execute git
2025-06-17 18:19:39.872 [error] Error getting git status: Failed to execute git
2025-06-17 18:19:39.878 [error] Error getting git status: Failed to execute git
2025-06-17 18:19:44.505 [error] Error getting git status: Failed to execute git
2025-06-17 18:20:43.084 [error] Git command failed: git log --pretty=format:"%H<|ENT|><|RY|>%s<|COM|><|MIT|>" -n 10 --author="$(git config user.email || git config user.name || whoami)" Command failed: git log --pretty=format:"%H<|ENT|><|RY|>%s<|COM|><|MIT|>" -n 10 --author="$(git config user.email || git config user.name || whoami)"
fatal: not a git repository (or any of the parent directories): .git

2025-06-17 18:20:43.084 [error] Error getting user commits: Command failed: git log --pretty=format:"%H<|ENT|><|RY|>%s<|COM|><|MIT|>" -n 10 --author="$(git config user.email || git config user.name || whoami)"
fatal: not a git repository (or any of the parent directories): .git

2025-06-17 18:20:43.599 [error] Git command failed: git rev-parse --show-toplevel Command failed: git rev-parse --show-toplevel
fatal: not a git repository (or any of the parent directories): .git

2025-06-17 18:21:32.428 [warning] Completed job unsuccessfully, will retry: .\memory-bank\projectbrief.md error: Bad unexpected error
2025-06-17 18:21:49.588 [warning] Completed job unsuccessfully, will retry: .\memory-bank\projectbrief.md error: Bad unexpected error
2025-06-17 18:21:49.588 [warning] Completed job unsuccessfully, will retry: .\memory-bank\productContext.md error: Bad unexpected error
2025-06-17 18:23:16.236 [error] Error getting git status: Failed to execute git
2025-06-17 18:23:31.998 [error] Error getting git status: Failed to execute git
2025-06-17 18:23:33.053 [error] Error getting git status: Failed to execute git
2025-06-17 18:23:34.009 [error] Error getting git status: Failed to execute git
2025-06-17 18:23:35.321 [error] Error getting git status: Failed to execute git
2025-06-17 18:23:37.466 [error] Error getting git status: Failed to execute git
2025-06-17 18:23:46.909 [error] Error getting git status: Failed to execute git
2025-06-17 18:23:47.903 [error] Error getting git status: Failed to execute git
2025-06-17 18:23:50.062 [error] Git command failed: git rev-parse --show-toplevel Command failed: git rev-parse --show-toplevel
fatal: not a git repository (or any of the parent directories): .git

There is no git repo set up. there is no .gitignore. I’ve tried deleting .gitconfig, tried creating a report and committing and creating all those files.

Tried going to codebase where I had repos set up.

I’ve tried deleting workspaceStorage.

Tried stopping/restarting/deleting indexing/restarting cursor/restarting system.

1 Like

Same

Version: 1.0.0
VSCode Version: 1.96.2
Commit: 53b99ce608cba35127ae3a050c1738a959750860
Date: 2025-06-04T19:21:22.523Z (1 wk ago)
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0
1 Like

It makes me feel much better to see you guys are experiencing it as well LOL. I’m sure they will fix it soon. Have a great day everyone, We all need to go outside anyway!

3 Likes

1 Like

I tried using background agents, but indexing isn’t working there either

Sorry for the delay, lots of fun things happening on the backend here. But it seems to be recovering now. Might take a little while to stabilize but can anyone confirm it’s working better now?

4 Likes

I can confirm that the progress bar is moving! Now at 20%, increasing ~10% per minute.

2 Likes

Working now, thanks!

1 Like

im starting to sync, slowly but its working.

1 Like

Fixed! Indexing works again! Thank you Cursor team

2 Likes