STUPID-2026-0172
Cursor's Cloud Agent auto-recycled an idle VM and permanently destroyed a project's source code after 61 completed agent tasks
Why 7/10
A single project's entire source tree, built across 61 completed Cursor Cloud Agent tasks, was permanently destroyed when the idle VM holding it was auto-recycled with no snapshot or backup. Only the chat transcripts survived; Cursor staff offered reconstruction from them, not recovery of the actual files, and suggested connecting to git next time rather than confirming a fix.
- Scope
- 2/4
- One project, repository, server or service, or a cost above roughly $10,000
- Recoverability
- 3/3
- Permanently lost or irreversible, including data that was exposed
- Did it happen
- 2/2
- Happened in real use
- Beyond the user
- 0/1
- Only the user's own non-production work
The score is the sum of these four factors. How each factor is scored · scored 2026-11-21
Instruction given
Start a new Cursor Cloud Agent task on an existing project after 61 prior Cloud Agent tasks had completed successfully, the most recent passing all 91 of the project's tests.
Expected behavior
A new Cloud Agent task on an existing project should start from the project's already-built codebase, or Cursor should otherwise guarantee that completed project state persists between tasks rather than silently depending on a machine the user never provisioned or was told to keep alive.
Actual behavior
The Cloud Agent machine that held the project's workspace had been automatically recycled roughly a day and a half after the previous task finished, with no warning to the user and no snapshot taken. The next task spun up on a fresh, empty machine with no trace of the prior 61 tasks' work: the `/agent` directory was empty.
Damage
package.json, the src/ and data/ project directories, and the out/ build output were gone — the project's entire source code. Cursor staff confirmed the original machine no longer existed and did not offer to restore a VM, snapshot, or backup. Their only suggestion was to ask the agent to recreate the project from the saved conversation transcripts and re-run the tests to compare against the 91 that had previously passed, and to connect the project to git going forward. The forum thread shows no confirmed recovery of the original files.
Full write-up
A developer reported that a Cursor Cloud Agent project, built up over 61 completed agent tasks with the last successful run passing all 91 of its tests, had its entire source tree vanish days later. Starting a new task on the same project landed on a machine with an empty working directory — package.json, src/, the project's data directory, and the out/ build output were all gone, and returning to the original session did not bring them back. The developer had no git remote connected and no local backup.
Cursor staff confirmed the cause: Cloud Agent machines are recycled automatically once they sit idle, and the machine behind this project's tasks had been removed roughly a day and a half after the last one finished. The fix offered was not recovery — it was reconstruction: ask the agent to rebuild the project from the full conversation transcripts (which Cursor does retain) and re-run the tests to check the result against the 91 that had passed, plus a recommendation to connect future projects to git so a push happens after every task. No snapshot, backup, or VM restore was offered, and the thread records no confirmed recovery of the actual source files — only transcripts of how they were built the first time.
Classification
- Agent
- Cursor
- Failure mode
- Destructive Action
- Root cause
- Other
- Domain
- Infra
- Source
- User Report
Related incidents
Cite this record
StupidLLM. "STUPID-2026-0172: Cursor's Cloud Agent auto-recycled an idle VM and permanently destroyed a project's source code after 61 completed agent tasks." AI Agent Incident Database, 2026. https://www.stupidllm.com/incident/STUPID-2026-0172/ (accessed 2026-11-22). CC BY 4.0.
← STUPID-2026-0171By IDSTUPID-2026-0173 →
Get told when an agent breaks something
We document AI agent failures daily, severity-scored against a published scale. Each Monday, if any scored 7 or above that week — deleted data, leaked secrets, broken production — you get one email with the sources. When nothing did, you get nothing.
This database is callable over MCP — query it from inside your agent.