Hey, thanks for the report. This looks like a race condition similar to an existing MCP-related issue we’re tracking (MCP Server Race Condition Causes Infinite Process Spawning on Windows (Cursor 2.0.34)), but affecting file indexing and git operations instead.
Quick diagnostic questions:
- Do you have any MCP servers configured in
~/.cursor/mcp.jsonor.cursor/mcp.json? - Approximately how many files are in your project?
- Is Codebase Indexing enabled? (Cursor Settings > Indexing & Docs)
Temporary solutions:
- Disable Codebase Indexing: Cursor Settings > Indexing & Docs (toggle off)
- Add .cursorignore: Create
.cursorignorein your project root and exclude build output directories - Temporarily disable Git integration: Marketplace >
@builtin git> disable Git extension > Reload Cursor
I’ll escalate this to the team as it’s making Cursor unusable. The rg (ripgrep) and git process spawning suggests the file watching system is creating one process per file change instead of batching them.
Could you also share the output from Help > Toggle Developer Tools > Console when the issue occurs?