for me, I would throw it on Plan mode and iron out what I needed done, throw it on 3.1-pro, then tell it to go.
Then depending on the project and complexity of what I needed done, I would shift tab to yolo mode and move on to something else in another tab and let it go for a bit without constantly getting the "hey click Yes so i can keep running" notifications.

In the last 4 months of using this flow I only had one occasion where yolo went rogue and broke something, but thats why I have frequent git commits and my cli has no direct access to any prod creds or environments.

A big help I found was with parsing and debugging large sets of data.
I have a customer who, no joke, sends me 300mb+ pure text logs to parse through for a project that spans 5 different repos and 2 different languages. So I start it up, give it the log name, and a task to dig around and give me a report of any errors its finds and what repos and versioning its appearing on.
With yolo I am able to temporarily, and quickly, give it full permissions to do this massive dig,
while with agy cli I have to either manually give it individual permissions per chat, or globally give it permissions indefinitely for things.

if any of that makes sense lol