Describe the Bug
AI-generated file changes are not written to disk immediately. Files remain in a pending/virtual state until manually opened and saved in the IDE. This blocks automation, batch edits, and efficient use of the AI for large projects. Manual review is required for every file, which is slow and error-prone.
Steps to Reproduce
- Use Cursor AI to generate or edit multiple files in a project.
- Do not manually open or save the files in the IDE.
- Attempt to access the files on disk or via terminal—only the frontmatter or placeholder is present, not the full content.
- Try to commit or use the files in other tools—changes are missing until each file is manually opened and saved in Cursor.
Expected Behavior
All AI-generated file changes should be written directly to disk immediately, just like manual edits, without requiring manual review or opening each file. This would allow for reliable automation, batch edits, and efficient workflows.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.1.7 (user setup)
VSCode Version: 1.96.2
Commit: 7111807980fa9c93aedd455ffa44b682c0dc1350
Date: 2025-07-01T07:38:05.103Z
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.26100
Additional Information
- This issue has been reported by multiple users in the Cursor Community Forum.
- Workarounds like restarting Cursor, changing permissions, or using terminal commands do not reliably fix the problem.
- References:
- Current workaround: Manually open and save each file after AI changes, or restart Cursor IDE (sometimes helps, but not reliable).
- After closing Cursor, (some) files still did not update (v1.7.1)
- Restarting Cursor, Cursor resaved some of the files that had changes outstanding.
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor