Hey, thanks for the report, and sorry this happened. I saw the screenshot with the error “We encountered an unexpected error repeatedly”.
I checked your agent. This happens when a Cloud Agent started as “New Project” later gets a real project name. Renaming changes the repo URL, but the original agent still points to the old one, so every follow-up in that chat fails with “Agent encountered an error”. We’re tracking this issue, and your report is attached to it.
Good news, your code is safe. Everything the agent managed to do is in the renamed repo under your account. To keep going:
- In Cursor, start a new Cloud Agent.
- When picking a repo, choose your project under the new name, not “New Project”.
- In the first message, briefly say where you left off. The new agent will start from the current state of the repo.
You won’t be able to resume the original chat, but nothing was lost in the repo. I can’t share a timeline for a fix yet, but I’ll post an update here if I have one. Let me know if the new agent gets stuck on anything.