You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bash permission deny rules in agent config not being enforced #11218
Bash commands that are explicitly denied in the agent's orchestrator.md permission config are executing without being blocked.
Steps to Reproduce
Create an agent config with bash permission deny rules:
permission:
bash:
"rm *": deny"*": allow
Run the agent and execute a denied command:
rm test-delete-me.md
Expected: Command should be blocked with a permission denied error
Actual: Command executes successfully
Evidence
# Created test file
$ echo"# Test File"> test-delete-me.md
# Attempted to delete (should have been blocked)
$ rm test-delete-me.md
# ✅ Executed without error - file was deleted
I don't think so, it's just the order in which permissions are loaded, in the end when "*": enable is loaded all the previous rules are overwritten. But maybe I'm wrong.
Activity
cravenceiling commentedon Jan 30, 2026
I think it’s because of the order of the permissions. I just tried this:
and it worked.
iamhenry commentedon Jan 30, 2026
ill try but that's still a bug, right?
cravenceiling commentedon Jan 30, 2026
I don't think so, it's just the order in which permissions are loaded, in the end when
"*": enableis loaded all the previous rules are overwritten. But maybe I'm wrong.rekram1-node commentedon Jan 30, 2026
not a bug the ordering is intentional and it is documented
iamhenry commentedon Jan 30, 2026
Good to know. Thx