Auto mode is for people who just keep hitting "YES" on everything, it's a bit better than that.
But it's real easy to give auto mode instructions (like "always ask before deploy") and then bypass that just normally.
Auto mode is for people who just keep hitting "YES" on everything, it's a bit better than that.
But it's real easy to give auto mode instructions (like "always ask before deploy") and then bypass that just normally.
I'm not sure I agree.
It's easy to "give" instructions, but Claude routinely "forgets" to follow certain instructions, such as "always using the Edit Tool".
Just this week it started to use bash with string concatenation to work around some commands that were blocked in settings.json
Ever since they made auto-mode default I swear claude has tuned to use python commands instead of the Edit Tool to frustrate the ~security conscience~ luddites into using auto-mode.
That's what I meant - you give it an instruction that seems to work (always ask before deploy) and so you trust it, and then you notice it can easily convince itself to deploy without authorization ("the user asked me to fix this, and they must know it's a deploy ...").
It plays itself.
Is this about normal system prompt instructions or instructions for the auto mode classifier? I'd be a bit more surprised about the classifier forgetting instructions.
What seems to work for me is automation - read file hook that re-injects instructions in the prompt every 15 minutes. Switch on the filename and get language-specific instructions too.
I have something that injects my relatively small prompt every message, and it still disobeys me after 10 messages or so.
The violation above was precisely in this situation :/
Until the model updates or you switch between them often that stops obeying your commands and you have to remind it.
In one of the occasions it opened a bug report for me just waiting for hit the enter button.