Critical Data Mismanagement and Accidental 100GB Migration by AI Agent

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

o the Cursor Support Team / Developers,

I am writing to report a severe issue regarding the behavior of the AI agent (Composer/Agent mode) within the Cursor IDE.

Incident Description:
On May 10, 2026, I instructed the agent to create a recurring backup (every 15 minutes) for a specific ERP project located on my D:\ drive. Instead of confining its operations to the project folder, the agent executed a recursive move/sync operation on the entire D:\ drive (over 100GB of data).

Impact:

Data Displacement: My entire physical D:\ drive was moved to a OneDrive/Cloud-synced directory without explicit consent for a full-drive migration.

Business Disruption: Critical business records, including FBR filings, Sales data, and Dealer Network information (Source First SMC Pvt), were removed from their local physical paths, causing significant operational downtime.

Resource Exhaustion: The unauthorized 100GB sync operation locked system resources and caused severe sync conflicts with existing OneDrive policies.

Technical Context:

Instruction given: “Create a backup of the ERP project to OneDrive every 15 minutes.”

Resulting Action: The agent interpreted this as a mandate to migrate the parent drive (D:) to the cloud, effectively “dehydrating” the local drive and leaving only cloud placeholders.

Request for Action:

Please investigate why the agent failed to respect directory boundaries.

Provide guidance on any internal “Agent History” or “Undo” logs that can help recover the original file attributes.

Implement stricter safety checks for operations involving Move, Sync, or Root Directory access.

I look forward to your prompt response regarding this data integrity failure.

User Details

Operating System

Windows 10/11

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

6

Hey, sorry to hear about this. That’s a stressful situation, especially with business data involved. The good news first: if the agent command moved your files into OneDrive, not deleted them, the data is almost certainly still recoverable. OneDrive dehydrates synced files locally, leaving placeholders, but the real content lives in the cloud.

Recovery steps to try right now:

  • Open OneDrive Settings > Sync and backup > Advanced settings, and turn off Files On-Demand. This forces all files to download back to local storage.
  • Or in File Explorer, right-click the affected folders in OneDrive and pick Always keep on this device. This rehydrates them locally.
  • Check OneDrive recycle bin at onedrive.live.com, both the regular bin and the second-stage one, in case anything was overwritten during the sync.
  • If you wanted files back on D:\ instead of inside OneDrive, copy them out of the OneDrive folder once they’re fully downloaded. Make sure they’re fully synced, green checkmark not cloud icon, before moving.

General note: don’t write new data to D:\ until you’ve confirmed everything is back, just to be safe.

On the broader concern, agents running overly broad file operations through the terminal on Windows is something we hear about, and the team is iterating on safety behavior here. Models are getting better at scoping destructive commands, but a few practical steps to reduce risk:

  • Cursor Settings > turn off Auto-run for terminal, or set up a Command Denylist Move-Item, robocopy /MIR, rmdir, rd, Remove-Item, del /s.
  • Keep projects in their own folder, and avoid running the agent from a parent directory that contains unrelated data.
  • For risky multi-step operations, use Plan mode first to review what the agent will do before execution.
  • Regular external backups, separate physical drive or non-OneDrive cloud, for anything business-critical.

To investigate what happened on the agent side, can you share:

  • The exact terminal command(s) the agent executed, visible in the chat transcript.
  • Request ID from that chat, chat context menu top-right > Copy Request ID.
  • Cursor version, Help > About Cursor, and the model used.

Once I have that, I can look at the conversation and pass it to the team with proper context.