Indexing tab missing in settings

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The Indexing tab is missing from the Cursor settings. For a specific project, we cannot allow indexing, so we need the ability to disable indexing for that project.

I urgently need clarification on whether indexing has been entirely disabled or removed as a feature, or whether it is now mandatory for all Cursor projects. At least confirmation, that the cursorindexingignore still works as it used to.

Steps to Reproduce

Update to 3.11.25

Expected Behavior

I either have an indexing tab that shows the status or clear documentation that this feature was removed. Currently your docs show that the indexing tab should still exist…

Operating System

MacOS

Version Information

Version: 3.11.25
VS Code Extension API: 1.125.0
Commit: fc2563ec93d793fc275eef734405a4fdf8b47b20
Date: 2026-07-15T01:27:41.754Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 25.5.0

Additional Information

For regulatory reasons, we will most likely have to partially suspend our use of Cursor until this issue is resolved.

Does this stop you from using Cursor

Yes - Cursor is unusable

Update: In Cursor 3.12.10, the Indexing & Docs tab is visible again, and the indexing controls appear to have been restored.

Thank you for addressing this so quickly.

For us, however, this is not merely a UI issue. Some of our repositories are subject to compliance requirements that prohibit indexing. When the documented interface for verifying, disabling, and deleting an index disappeared without notice or accompanying release notes, we could not safely assume that the underlying indexing behavior had remained unchanged.

Could you please confirm:

  1. whether this was exclusively a UI issue;
  2. whether existing indexing settings remained effective while the tab was unavailable;
  3. whether .cursorindexingignore continued to be applied without any behavioral changes

Restoring the tab resolves the immediate operational issue for us. An official confirmation regarding the underlying behavior would help us complete our internal compliance assessment.

Hey there!

We shared some news/context about this over here:

Please engage or comment on that thread if you’d like to discuss this further!