Cursor delete files

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The problem is that I do not currently have more technical details, logs, or a reliable repro sequence to provide.

What I do remember consistently is that every time the issue happened, Cursor would first become unresponsive for a long period and display messages such as “Model is busy” or “Model can’t respond, try again later”. Immediately after that, I would discover one of the following:

  • Files deleted
  • Untracked files missing
  • Git state rolled back to an older version

This pattern happened multiple times.

I have already tried different environments:

  • Windows desktop
  • WSL
  • Remote VPS servers
  • Docker containers

I observed the same behavior across all of them.

What makes me suspicious is that the issue appears right after Cursor loses connection to the model or reports that the model is unavailable. The timing is consistent enough that I cannot ignore it.

Also, my connection quality is excellent:

83 ms
83 ms
79 ms
78 ms
83 ms
79 ms
78 ms
82 ms
78 ms
but the slowest is
[2026-06-03T10:29:51.337Z] Starting stream
[2026-06-03T10:29:52.071Z] Response: ‘foo’ in 680ms
[2026-06-03T10:29:52.791Z] Response: ‘foo’ in 720ms
[2026-06-03T10:29:53.791Z] Response: ‘foo’ in 1000ms
[2026-06-03T10:29:54.792Z] Response: ‘foo’ in 1001ms
[2026-06-03T10:29:55.786Z] Response: ‘foo’ in 994ms
[2026-06-03T10:29:56.779Z] Result: true

So this does not appear to be a local network issue.

At this point, I am not claiming I know the root cause. I am simply reporting a repeated pattern that I have observed multiple times and hoping the team can investigate whether there is any connection between agent/model failures and the file or Git behavior that follows.

Steps to Reproduce

I have already tried different environments:
Windows desktop
WSL
Remote VPS servers
Docker containers

but same bug

Expected Behavior

cursor should no remove files

Operating System

Windows 10/11

Version Information

Version: 3.6.31 (system setup)
VS Code Extension API: 1.105.1
Commit: 81fcf2931d7687b4ff3f3017858d0c6dee7e2a60
Date: 2026-05-31T17:46:29.630Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.220
OS: Windows_NT x64 10.0.28000

Does this stop you from using Cursor

No - Cursor works, but with this issue

Thanks for starting a separate thread. That way your case won’t get lost in the details of the original one.

I’ll summarize what we agreed on in the last discussion. With your setup File Deletion and External File Protection enabled, and Auto Run in allowlist mode with read only commands only, the agent can’t run a destructive shell command by itself without an approval popup. So what you’re describing now untracked files disappearing and the repo rolling back to older states looks less like a shell delete and more like a separate checkpoint or state restore mechanism. There’s a known pattern where untracked files can disappear after a window reload. It’s on our radar, but I don’t have an exact ETA for a fix.

One technical note just in case. Aliases in ~/.bashrc like alias rm='rm -i' don’t work on Windows. The agent runs commands via cmd.exe or PowerShell, not bash. So those aliases won’t help as protection here.

What would really move this forward is a repro. If you catch it happening again, please send:

  1. Exact steps. What happens right before the files disappear, like a window reload, a git action by the agent, and what the agent says.
  2. What you see in the agent chat at that moment. Which tool calls or commands it runs.
  3. The Request ID for that session. Chat menu in the top right > Copy Request ID. With Privacy Mode on, the ID may be limited.

For recovering what already rolled back:

  • git reflog often lets you get back even after stash or reset. Find the right HEAD, then git reset or git checkout to it.
  • Local History in the IDE. Cmd/Ctrl+Shift+P > Local History. It keeps file versions, including files not tracked by git.

Please send the repro and Request ID when you have them, and I’ll link it to the right tracked issue so we can dig in.