4 ms·
> Claude Code used bash to make edits anyway. If you had the former rule why would you ever whitelist bash commands? That's full access to everything you can d
by godelski 6mo ago
> Claude Code used bash to make edits anyway.
If you had the former rule why would you ever whitelist bash commands? That's full access to everything you can do.
Same goes for `find`, `xargs`, `awk`, `sed`, `tar`, `rsync`, `git`, `vim` (and all text editors), `less` (any pager), `man`, `env`, `timeout`, `watch`, and so many more commands. If you whitelist things in the settings you should be much more specific about arguments to those commands.
People really need to learn bash
- esafak 6mo agoAt some point you need to get things done.
- godelski 6mo agoThere's no point in getting things done if there's nothing that ends up being done. You can still get shit done without risking losing it all. Don't outsource your thinking to the machine. You can't even evaluate if what it is doing is "good enough" work or not if you don't know how to do the work. If you don't know what goes into it you just end up eating a lot of sausages.
- enochthered 6mo agoYeah you’re not wrong. I hadn’t accounted for the model working around it and that’s on me. The whitelist is much more specific now.