[xnorswap]

Yes, this is why I generally still use "ask for permission" prompts.

As tedious as it is a lot of the time ( And I wish there was an in-between "allow this session" not just allow once or "allow all" ), it's invaluable to catch when the model has tried to fix the problem in entirely the wrong project.

Working on a monolithic code-base with several hundred library projects, it's essential that it doesn't start digging in the wrong place.

It's better than it used to be, but the failure mode for going wrong can be extreme, I've come back to 20+ minutes of it going around in circles frustrating itself because of a wrong meaning ascribed to an instruction.

[lachlan_gray]

fwiw there are more granular controls, where you can for example allow/deny specific bash commands, read or write access to specific files, using a glob syntax:

https://code.claude.com/docs/en/settings#permission-settings

You can configure it at the project level

[xnorswap]

Yes, those permissions stick with the project in the settings file. I'd like those same permissions, but configurable per-session / context.

[the_harpia_io]

oh man the going-in-circles thing - that's the worst because you don't even know how long to let it run before you realize it's stuck. I've had similar issues where it misunderstands scope and starts making changes that cascade in ways it can't track. the 'allow this session' idea is actually really good - would be useful to have more granular control like that. honestly this is why I end up breaking work into smaller chunks and doing more prompt-response cycles rather than letting it run autonomously, but that obviously defeats the purpose of having an agent do the work