Describe the Bug
In cursor the agent opens every file it edits.
This functions as a child process zombie attack to system memory on large codebases.
When the app is open too long the agent will. Gain increased api failures due to taking up too much memory with all the open files.
There is no obvious indicator that during this session the agent has opened 200 files.
Should at least be a setting.
Steps to Reproduce
Clear all files from the view. Ask cursor to make changes. It will open every file it edits into the viewer. Keep the editor open on a codebase with hundreds to thousands of files. This will cause your computer to start freezing and cursor api failures to increase dramatically.
Expected Behavior
It should not open files into viewer unless requested or a user has already opened it. File writing should just happen via IO.
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
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
Does this stop you from using Cursor
No - Cursor works, but with this issue