Cursor broke or deleted your code. Recovery, in order.

First: don't let the agent "fix" anything yet. The most common way recoverable damage becomes permanent is an AI helpfully rewriting files from memory over the top of what could have been restored. Recovery first, rebuilding last.

1. Restore the checkpoint

In Cursor's chat panel, every agent request has a restore control that returns your files to the state before that request ran. Find the message where things went wrong and restore to just before it. This handles most cases in under a minute.

2. Per-file local history

Cursor keeps a local history of every file on your machine. Open a damaged file, open the Timeline panel (bottom of the Explorer sidebar), and click back through earlier versions. Tedious across many files, but it works even after the chat that did the damage is long gone.

3. Any copy that lives elsewhere

If the project was ever synced or pushed anywhere (GitHub, a project home, even a zip you emailed someone), that copy is untouched by whatever happened locally. You lose only the work since the last save there.

4. Only now, rebuild

For whatever the first three couldn't recover, paste this before anything else:

Why this keeps happening with agents

Agent-mode tools edit many files fast, and their mistakes come in batches: nine files subtly wrong beats one file obviously wrong for damage. Cursor's own protections (checkpoints, local history) are per-session and per-file. The protection that actually matches agent-scale mistakes is project-level: every working state saved somewhere off the machine, restorable as a whole. That's the entire design of Plyo: your agent saves each working version to a timeline as it goes (one paste to set up), and "put everything back to when it worked" becomes one click instead of an afternoon of file archaeology.