Local file deletion upon first use

[coral sun]

What is the intended behavior for adding local folders with git repos? I was thinking about coming over from Cursor.

It showed a TON of uncommitted changes, and I thought the ai had taken the liberty of immediatetly altering files, so i rejected the commits.

What happened next was every single one of my uncommitted files to git were either deleted or written to 0 bytes. I thought I had pushed recently, but I hadn't. Warp effectively deleted the entirety of my project from my local disk, blowing hundreds of credits used in cursor the last week and at 60-70 hours of work.

[mint rune]

Hi @coral sun. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

---

I'm very sorry to hear about your experience and the loss of your work. This is a serious issue that needs immediate attention.

Based on the knowledge sources, there are several documented issues related to git changes and file management in Warp:

Known Issues with Git Changes

The knowledge sources reveal multiple reports of problems with uncommitted changes:

1. Uncommitted changes being lost or committed unexpectedly - There are documented cases where uncommitted changes were committed when running commands, and instances where git changes were removed when splitting panes.

2. Git alias conflicts - Some issues were traced to git aliases (like comm or gcreset) that conflicted with Warp's git integration, causing unexpected behavior with uncommitted changes.

3. AI autonomy concerns - There's a documented issue about AI deleting files without permission, where users reported the AI would delete files and directories without asking for confirmation.

What You Should Do

Immediately:

1. Do not use Warp in this directory until you understand what happened
2. Check if you have any git aliases that might conflict (especially ones starting with comm or involving git checkout)
3. Look for any git recovery options - check git reflog to see if there's any way to recover your work

For the Warp team:
Your situation appears to be a critical bug that goes beyond the documented issues. The knowledge sources mention that one user noted you should not use Warp in agent/autonomy mode outside of a directory under version control, but your case involves a git repository where files were actually deleted.

I strongly recommend:

1. Filing a critical bug report with Warp immediately
2. Including detailed logs (following these instructions)
3. Contacting Warp support directly about this data loss incident

The knowledge sources do not explicitly describe the intended behavior when opening a local folder with a git repo for the first time, nor do they explain why rejecting commits would result in file deletion. This appears to be a severe bug that needs urgent investigation by the Warp team.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: