Cursor Codebase Indexing Failing with Persistent Handshake Timeouts on New Repository

Bug Reports
1

Describe the Bug

When opening a newly cloned repository in Cursor for the first time, the codebase indexing system fails consistently with handshake timeouts to Cursor’s indexing servers. Git indexing completes successfully, but codebase indexing fails with STATUS_FAILURE responses and eventual timeout errors. This prevents code intelligence features from working properly.

Steps to Reproduce

  1. Clone a new repository locally to C:\Users\[user]\[project]
  2. Open the project in Cursor for the first time
  3. Observe indexing process in the logs
  4. Notice that Git indexing succeeds but codebase indexing fails repeatedly
  5. Check logs showing handshake failures with increasing timeout intervals (4s → 8s → 16s → 32s → 64s → 128s)

Expected Behavior

  • Cursor should successfully establish connection with indexing servers (https://repo42.cursor.sh and https://api2.cursor.sh)
  • Codebase indexing should complete successfully for new repositories
  • Code intelligence features should be available immediately
  • Both Git indexing and codebase indexing should work without errors

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.2 (user setup)
VSCode Version: 1.99.3
Commit: faa03b17cce93e8a80b7d62d57f5eda6bb6ab9f0
Date: 2025-07-07T06:19:13.016Z (1 day ago)
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

Additional Information

Repository Details:

  • Project Type: React/TypeScript with Vite, Tailwind, and Supabase
  • Git Status: Properly configured (git remote -v and git config --get remote.origin.url work correctly)
  • Repository is newly cloned, first time being indexed by Cursor

Error Patterns:

  • Initial error: NoWorkspaceUriError and Git command failed: git config --get remote.origin.url (despite git working correctly)
  • Handshake failures: Consistent {"status":"STATUS_FAILURE","codebases":[]} responses
  • Final timeout: Error: timeout in handshake with retry

Key Observations:

  • Git indexing works perfectly: “Secondary handshake successful. Found 1 histories” and “Job completed. Total indexed: 0 PRs + 37 ignored + 0 failed”
  • Codebase indexing fails completely with server connection issues
  • Issue is reproducible across multiple restart attempts
  • User has opted out of PR indexing via configuration

Sample Error Logs:

2025-07-08 18:06:09.676 [info] Handshake timing: 1699.5946000000004, response: {"status":"STATUS_FAILURE","codebases":[]}
2025-07-08 18:11:19.661 [error] Error: timeout in handshake with retry
2025-07-08 18:11:19.662 [error] Handshake failed.

Does this stop you from using Cursor

Yes - Cursor is unusable

4 Likes
2

A post was merged into an existing topic: Cursor Stuck at Codebase Indexing