Allowlisting some Bash commands is often the same as allowlisting all
1–10 of 27 posts
Re: Allowlisting some Bash commands is often the same as allowlisting all
#2“…with Claude Code”
Re: Allowlisting some Bash commands is often the same as allowlisting all
#3“…with Claude Code”
Are there any agent permission systems that do this correctly?
Re: Allowlisting some Bash commands is often the same as allowlisting all
#4Same thing for allowing specific sudo-commands. Many tools (like vim or the tools mentioned in the article) would have the same problem when allowing them to be run with root privileges.
Re: Allowlisting some Bash commands is often the same as allowlisting all
#5Allowing a "command" (executable, I believe) that isn't a read-only absolute path is a fool's errand. I will modify PATH and run my own implementation of it.
Re: Allowlisting some Bash commands is often the same as allowlisting all
#6Same thing for allowing specific sudo-commands. Many tools (like vim or the tools mentioned in the article) would have the same problem when allowing them to be run with root privileges.
Re: Allowlisting some Bash commands is often the same as allowlisting all
#7I know they’re just being through but the “go test” part is a bit “Pray, Mr Babbage”… Test code is just code. I know of no language where tests are sandboxed in any meaningful way.
Re: Allowlisting some Bash commands is often the same as allowlisting all
#8everything is a container these days, and yet somehow collective-we don't manage to have AI agents run in a container layer on top of our current work, so we can later commit or rollback?
Re: Allowlisting some Bash commands is often the same as allowlisting all
#9“…with Claude Code”
The same caveats would apply to most kinds of restricted shell environments.
Re: Allowlisting some Bash commands is often the same as allowlisting all
#10[deleted]