Cursor can no longer index codebase

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Yesterday everything worked fine. Today, I installed the update that it prompted me to when I opened the IDE. Now when I open any repo in the IDE and typing ‘Index the codebase’ in the AI chat, I get the following:

Tried indexing from /path/to/codebase using cursor index, but the cursor CLI isn’t available on this system (command -v cursor returns nothing). I can proceed once the Cursor CLI is installed or if there’s another indexing command you’d like me to use.

Steps to Reproduce

  • Run Cursor IDE v2.1.32 on MacOS.
  • Open a codebase.
  • Type ‘Index the codebase’ in the AI chat.
  • Observe it fail to index the codebase with the same or similar response.

Expected Behavior

I expect it to complete indexing the codebase, provide a summary of the codebase, and ask me what I want to do next.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.32 (Universal)
VSCode Version: 1.105.1
Commit: ef979b1b43d85eee2a274c25fd62d5502006e420
Date: 2025-11-25T05:00:12.749Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.1.0

Does this stop you from using Cursor

Yes - Cursor is unusable

2

Hi there - that’s new to me that “Index the codebase” command from the Agent chat expects the Cursor CLI to be available. You can still generate an index directly from the UI:

  1. Open Cursor Settings, and navigate to the “Indexing & docs” area.
  2. In the Codebase section, click Compute index for the opened project.
  3. Wait for the progress bar to reach 100%.

image
image1428×1050 68.9 KB

In my own project, the UI index reaches 100% and recreating it works fine, too. I do have the Cursor CLI - I am not certain if the IDE depends on the CLI to perform this indexing.

image
image1414×1272 74.3 KB

Let me know what you find from the UI, and we’ll pick it up from there.

3

Hi arun,

Thanks for taking a look. I think we are good here. I just completely uninstalled and reinstalled Cursor. I think something got corrupted with the install as I just migrated to a new MacBook over the weekend via Time Machine. After reinstalling, Cursor appears to be working correctly now.

1 Like