Where does the bug appear (feature/product)?
Cursor CLI
Describe the Bug
Bug Report: Cursor Agent Process Using Excessive CPU (80-100%+)
Summary
Cursor’s agent/indexing process is consuming 80-100%+ CPU, causing significant performance degradation and requiring manual process termination. The issue occurs during normal usage of Cursor in a Rails project.
Environment
- OS: macOS 25.1.0 (Darwin)
- Cursor Version: 2025.11.06-8fe8a63 (based on agent path)
- Project Type: Rails 8.1.1 application
- Ruby Version: 3.4.7
- Node Version: 24.11.0
Issue Description
The Cursor agent process (cursor-agent) consistently uses 80-100%+ CPU, making the system unresponsive. The process must be manually killed to restore normal performance. This occurs during normal Cursor usage, not during any specific action.
Technical Details
Process Information
Process: /Users/qbantek/.local/share/cursor-agent/versions/2025.11.06-8fe8a63/node
Command: node --use-system-ca /Users/qbantek/.local/share/cursor-agent/versions/2025.11.06-8fe8a63/index.js --resume=af36cb01-869a-4c88-8590-75574faac4f0
CPU Usage: 94.2% (observed), previously 100%+
Memory Usage: ~787MB
Project Configuration
The project has the following language server configurations:
- Ruby LSP: Configured with
ruby-lspandruby-lsp-railsgems - JavaScript/TypeScript: Standard JavaScript files (no TypeScript)
- Build Tools: esbuild (watch mode) and nodemon (CSS watch)
Project Structure
- Rails 8.1.1 application
- JavaScript bundling with esbuild
- CSS compilation with Sass/PostCSS
- Development watch processes running via Foreman (
bin/dev)
Actual Behavior
- Agent process uses 80-100%+ CPU continuously
- System becomes unresponsive
- Process must be manually killed
- Issue recurs after restarting Cursor
Additional Context
- The issue appears to be with Cursor’s own indexing/agent process, not a language server
- Ruby LSP is configured but not actively running when the issue occurs
- The project has standard Rails structure with no unusual configurations
- Watch processes (esbuild, nodemon) are running but are separate from the problematic process
Workarounds Attempted
- Manually killing the process (temporary fix)
- Restarting Cursor (issue recurs)
- No permanent solution found
Request
Please investigate why the Cursor agent process is consuming excessive CPU and implement fixes to:
- Limit CPU usage during indexing
- Prevent runaway indexing processes
- Add automatic throttling or process management
Steps to Reproduce
Steps to Reproduce
- Open the Rails project in Cursor
- Use Cursor normally (editing files, navigating code)
- Monitor CPU usage via Activity Monitor or
ps aux - Observe Cursor agent process consuming 80-100%+ CPU
- Issue persists until process is manually terminated
Expected Behavior
Expected Behavior
Cursor’s agent/indexing process should:
- Use reasonable CPU resources (<20% during normal operation)
- Complete indexing without sustained high CPU usage
- Not require manual intervention to restore system performance
Screenshots / Screen Recordings
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Environment
- OS: macOS 25.1.0 (Darwin)
- Cursor Version: 2025.11.06-8fe8a63 (based on agent path)
For AI issues: which model did you use?
Auto, an agent router designed by Cursor
For AI issues: add Request ID with privacy disabled
70734489-f251-4cfc-bee1-2b046c57a04e
Additional Information
Additional Information
If logs, diagnostics, or additional system information would be helpful, please let me know what you need and I can provide it.
Does this stop you from using Cursor
Yes - Cursor is unusable