YOLO mode ignoring user requests

### What happened?

Claude code has a mode --dangerously-skip-permissions which leaves the User in control of orchestration, but stops prompting for tool requests repeatedly which slows down the process.

It seems Gemini only has a --YOLO mode to do something similar, but then it just takes over orchestration of everything, assuming it can do UAT testing, making changes when I just ask for a status update, etc. I have previously asked Gemini to write a memory to prevent it from doing this, but it seems on every new start of Gemini cli this gets forgotten and I'm back to the situation where Gemini assumes it knows best and never involves me in any query.

Either we need a lighter form of --YOLO where the user remains the orchestrator, but gemini-cli stops prompting for tool use, OR we need gemini-cli to actually read and obey the instructions in gemini.md. (Preferably both, since ignoring explicit instructions in gemini.md is pretty bad behaviour)

[bug-report-history-1779779366326.json](https://github.com/user-attachments/files/28251947/bug-report-history-1779779366326.json)

### What did you expect to happen?

I expected Gemini to obey gemini.md instructions, or to offer me a way to have it skip tool prompts only.

### Client information

* **CLI Version:** 0.43.0
* **Git Commit:** c0775c38b
* **Session ID:** 902f7a75-aa18-4d9b-a7ed-40a8c2cca6b9
* **Operating System:** win32 v26.1.0
* **Sandbox Environment:** no sandbox
* **Model Version:** auto-gemini-3
* **Auth Type:** oauth-personal
* **Memory Usage:** 278.8 MB
* **Terminal Name:** Unknown
* **Terminal Background:** #0c0c0c
* **Kitty Keyboard Protocol:** Unsupported

### Login information

Google Account

### Anything else we need to know?

_No response_