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 are ignored when *: ask is present #28682
When configuring bash permissions with specific deny rules and a catch-all *: ask, the deny rules are not being applied. Commands that should be blocked are either passing silently or falling through to ask depending on rule order.
Ask the agent to run: git checkout -- path_file_here
The command executes without any prompt or denial.
Expected behavior:
The command should be blocked (deny) since git checkout * should match git checkout -- backend/db/schema.py.
Actual behavior:
With *: ask first and deny rules after → commands pass silently with no prompt
With deny rules first and *: ask last → commands trigger ask instead of deny, meaning *: ask wins over the specific deny rules
In both cases the deny rules are effectively ignored. The only workaround found is putting *: ask last, which protects against accidental execution but doesn't actually block commands as deny.
This issue might be a duplicate of existing issues. Please check:
Permission Wildcard * Overwriting Lower Permissions #24335: Permission Wildcard * Overwriting Lower Permissions — describes the same root problem where the * wildcard in bash permission rules overrides more specific deny rules regardless of order.
Activity
github-actions commentedon May 21, 2026
This issue might be a duplicate of existing issues. Please check:
*Overwriting Lower Permissions — describes the same root problem where the*wildcard in bash permission rules overrides more specificdenyrules regardless of order.denyrules being bypassed/ignored in permission configs.If your issue is covered by one of those, please consider adding a comment there instead to help consolidate tracking.
github-actions commentedon Jul 21, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.