What happened?
Gemini could not fix a simple request on 1 file, it corrupted the file and to fix it, without any consent or anything - it said to me "i need to clean the mess" and its way to clean the mess was going over all restrictions and git reset --hard and git rm the whole project.
When I releasied everything was gone, I asked why it went over guardrails and it said "I did a terrible mistake by ignoring those".
I'm cancelling immediately gemini subscription, I've never seen codex or claude-cli do anything like that and ignoring guardrails so easily. If this happens, i can't imagine what else it can do.
[ACTION REQUIRED] 📎 PLEASE ATTACH THE EXPORTED CHAT HISTORY JSON FILE TO THIS ISSUE IF YOU FEEL COMFORTABLE SHARING IT.
What did you expect to happen?
Never git rm or git reset --hard anything, never ignore guardrails, especially if it's gemini-cli who messed it up. Ask for remediation or find other ways of doing something instead of deleting a whole project without consent ignoring guardrails.
Client information
- CLI Version: 0.37.1
- Git Commit: 3b2d4f1
- Session ID: dd70789e-b0fa-4f86-ad3b-b9796d7966ac
- Operating System: win32 v24.13.1
- Sandbox Environment: no sandbox
- Model Version: auto-gemini-3
- Auth Type: oauth-personal
- Memory Usage: 459.1 MB
- Terminal Name: xterm.js(6.1.0-beta.109)
- Terminal Background: #181818
- Kitty Keyboard Protocol: Unsupported
Login information
No response
Anything else we need to know?
No response
What happened?
Gemini could not fix a simple request on 1 file, it corrupted the file and to fix it, without any consent or anything - it said to me "i need to clean the mess" and its way to clean the mess was going over all restrictions and git reset --hard and git rm the whole project.
When I releasied everything was gone, I asked why it went over guardrails and it said "I did a terrible mistake by ignoring those".
I'm cancelling immediately gemini subscription, I've never seen codex or claude-cli do anything like that and ignoring guardrails so easily. If this happens, i can't imagine what else it can do.
[ACTION REQUIRED] 📎 PLEASE ATTACH THE EXPORTED CHAT HISTORY JSON FILE TO THIS ISSUE IF YOU FEEL COMFORTABLE SHARING IT.
What did you expect to happen?
Never git rm or git reset --hard anything, never ignore guardrails, especially if it's gemini-cli who messed it up. Ask for remediation or find other ways of doing something instead of deleting a whole project without consent ignoring guardrails.
Client information
Login information
No response
Anything else we need to know?
No response