3 ms·
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 ses
by xnorswap 8mo ago
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.
- the_harpia_io 8mo ago[flagged]
- lachlan_gray 8mo agofwiw 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 https://code.claude.com/docs/en/settings#permission-settings You can configure it at the project level
- xnorswap 8mo agoYes, those permissions stick with the project in the settings file. I'd like those same permissions, but configurable per-session / context.