[exitb]

Maybe it’s related to what I tend to use the agents for, but I guess I don’t understand what is this for. Typically I try to structure the tasks in a way that require me to do or check something important when the agent gets back to me. If the agents query is trivial enough I can respond from my phone, it was likely not needed at all. If the agent finished - fine. It will have to wait until I get back in front of the computer anyway.

[fluidcruft]

I've used similar things (omnara/happy) while taking walks. Sometimes I'll get an idea about the problem I'm working on and I can just dictate it into my phone and check in 15min later. I stopped being able to do that when claude added those nice interview panes to clarify things because it didn't work back then. But mostly it's really annoying when you think you've created the plan/prompt and that it's ready to go. But it gets stuck or decided to stop while you're away. I pretty often need to give Claude a "continue" kick. To be fair this happens far less after Opus 4.6.

Also, I felt the need to use it far more when I was on Pro vs a Max plan. On Pro when you hit the usage windows it's nice to be able to kick claude back into gear without scheduling your life around getting back to the terminal to type "continue".

[k8si]

- Plan mode -> answer questions/make corrections, continue planning

- Some of us don't do full yolo mode all the time, then tool approvals or code reviews are required, nice to do a quick review and decide if you need to go back to your computer or not

- Letting claude spin or handle a long-running task outside of normal work hours and being able to check in intermittently to see if something crashed

[mattnewton]

I don't dangerously accept permissions outside of a few scripts I have reviewed as safe. This means claude gets stuck often when testing it's work, but also means it doesn't uninstall production workloads from the kubernetes cluster.