Re:Claude Code's "Don't Ask Again" exposes passwords in 1,12...
by smallnamespace on Saturday November 07, 2026 @06:58PM
(#50409209)
[delayed]
Re:Claude Code's "Don't Ask Again" exposes passwords in 1,12...
by RHSeeger on Saturday November 07, 2026 @07:16PM
(#50409335)
> That is not the niche case, that's the dominant use of models.
It would be helpful to distinguish between your own opinion on how models ought to be used, compared to how others actually use models.
Re:Claude Code's "Don't Ask Again" exposes passwords in 1,12...
by zahlman on Sunday November 08, 2026 @12:11AM
(#50410575)
> That is not the niche case, that's the dominant use of models.
And if everyone else jumped off a bridge, I mean, used raw interpolation for SQL queries, would you do it too?
Re:Claude Code's "Don't Ask Again" exposes passwords in 1,12...
by literalAardvark on Sunday November 08, 2026 @02:42AM
(#50411202)
Don't worry, you can just use the automated approver to escape your queries! It's so secure!
Re:Claude Code's "Don't Ask Again" exposes passwords in 1,12...
by foldr on Sunday November 08, 2026 @07:14AM
(#50412592)
Using raw SQL string interpolation doesn't get you anything much that you can't get just as easily with a parameterized query. In contrast, properly sandboxing agents is such a pain, and such a productivity drain, that hardly anyone does it in practice, save for a vocal minority online.
Re:Claude Code's "Don't Ask Again" exposes passwords in 1,12...
by wongarsu on Saturday November 07, 2026 @08:07PM
(#50409602)
Auto mode seems to have some reasonable restrictions baked in. For example if you give claude access to two k8s namespaces, seriousproject-qa and seriousproject-prod, auto-mode will grant `kubectl exec` on the qa environment while denying the same command for the production environment. Of course you should be enforcing that by restricting what kind of access tokens you give claude access to, but auto-mode does have opinions about this stuff too, even if it's not bulletproof
However I do share your desire for a better manual mode. Auto-mode is both sometimes surprisingly lax, and sometimes too restrictive. Maybe manual mode should inject a reminder "keep your commands as simple one-liners", the same way plan mode injects a reminder that you are in plan mode and don't want any code changes
Many of the problems when it comes to the manual approval feel like they stem from the expectation of using auto mode in the first place. After all, what's the point of improving the manual approval and safety matching if auto mode is the end all be all, and what's the point of training the model to output commands in a manner that can be parsed by a human if auto mode is always meant to be used? It's very rare for me to not see "command could not be statically analyzed", because the model keeps outputting bash golf.